You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2019. It is now read-only.
(This also affects how they're advertised in .well-known/openid-configuration).
It would be preferable to allow a consumer app to specify which URI path to mount these endpoints on. Sort of like:
letprovider=newProvider({issuer: 'https://example.com',mount: '/oidc/'})// -> which would lead to:// https://example.com/oidc/authorize// https://example.com/oidc/token// https://example.com/oidc/userinfo// etc
Note: This is only a refactoring of the provider's discover() functionality, not anything to do with OP express routes.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the various OIDC-related API endpoints are hardcoded in the Provider's constructor:
(This also affects how they're advertised in
.well-known/openid-configuration
).It would be preferable to allow a consumer app to specify which URI path to mount these endpoints on. Sort of like:
Note: This is only a refactoring of the provider's
discover()
functionality, not anything to do with OP express routes.The text was updated successfully, but these errors were encountered: