Support custom URI scheme redirection about authentik HOT 4 CLOSED

The only difference is that for the oauth2 provider, redirect URIs are validated against the list, and for a normal logins, only relative URIs are allowed.

But since the redirect comes from the OAuthFulfillmentStage and not the flow executor, this is very easy to add.

from authentik.

Sounds good, do you happen to have a stacktrace where that error is thrown?

The only interesting thing about this could be validating the destination URI, since IIRC the final redirect is done by the FlowExecutor, and not the OAuth Provider

from authentik.

Would the validation of the redirect URI with a custom scheme be any different compared to the HTTPS scheme?

Traceback (most recent call last):
File "/authentik/flows/views.py", line 152, in get
stage_response = self.current_stage_view.get(request, *args, **kwargs)
File "/authentik/providers/oauth2/views/authorize.py", line 264, in get
return redirect(self.create_response_uri())
File "/usr/local/lib/python3.9/site-packages/django/shortcuts.py", line 41, in redirect
return redirect_class(resolve_url(to, *args, **kwargs))
File "/usr/local/lib/python3.9/site-packages/django/http/response.py", line 504, in init
raise DisallowedRedirect("Unsafe redirect to URL with protocol %s" % parsed.scheme)
django.core.exceptions.DisallowedRedirect: Unsafe redirect to URL with protocol 'com.example.app'

from authentik.

This seems to be broken again starting with 2024.2.0

from authentik.