Allow Custom Redirect URL for OIDC and Google #495
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is now possible to specify a custom redirect url for the OIDC and Google provider. Since we only have to get the "code" parameter to finish the authentication flow, it doesn't matter if the site is hosted at kubenav.io or a user hosts them by themself. For the user it has not to allow kubenav.io as redirect url.
The following html files can be hosted at the provided redirect url to make it easier to copy the token: