This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
Bypass consent page #190
-
Sometimes for trusted/internal client app, we don't want to display consent to end-user, is there any configuration skip/bypass consent page for certain client ? |
Beta Was this translation helpful? Give feedback.
Answered by
babelouest
Oct 22, 2021
Replies: 1 comment 1 reply
-
You can skip the consent page by adding the query parameter If the user session is valid and has the expected credentials, the consent page will be automatically skipped. If the user session isn't valid or the password has expired or no scopes have been granted for example, then the consent page will be displayed anyway. The url would look like that: |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
babelouest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You can skip the consent page by adding the query parameter
g_continue
to the/auth
endpoint.If the user session is valid and has the expected credentials, the consent page will be automatically skipped.
If the user session isn't valid or the password has expired or no scopes have been granted for example, then the consent page will be displayed anyway.
The url would look like that:
https://glewlwyd.tld/api/oidc/auth?response_type=code&scope=openid&nonce=abcd&state=xyz&client_id=xxx&redirect_uri=https://example.com&g_continue