Last Updated: Dec 17, 2024
Overview
After following the instructions on marking the integration as First-party - there seems to be no way to avoid the consent prompt when completing authentication. It also does not “remember” that consent was given, and every authentication event causes it to re-prompt again for consent.
This article details how to get past this issue.
Applies To
- First-party applications
- Consent Prompt
- Login
Cause
The /authorize request included “prompt=consent” on every request. When redirecting to the /authorize endpoint, including the prompt=consent parameter will force users to provide consent, even if they have an existing user grant for the application and requested scopes.
Solution
Removing “prompt=consent” from the /authorize request restored the default behavior. More information on user consent can be found here.