feat: support for OIDC authentication #880
Open
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.
A prototype to enable OIDC support for #809.
How to test:
docker-compose -f docker-compose.oidc.yml up -d
, which uses Soluto/oidc-server-mock for a simple OIDC server provider, configured with one client ID and two user accounts.Load kutt login page http://localhost:3000/login
You should see a "Login with OIDC" button (actually a link) at bottom:
Clicking the link redirects you to http://7f000101.nip.io:8080/
OIDC_ISSUER
should point to a real OIDC provider such as Google or Facebook.Login with the user accounts defined in docker-compose. Successful login should redirect back to kutt homepage.
If the user does not exist, it is created with a random password, with email verified.
The passport strategy of
openid-client
package requires express sesssion to be enabled. For cookie-session, it creates cookie like this:What are still missing in this PR: