Allowing Clients To Skip Consent
Companies that have internal applications that use OAuth 2.0 or OpenID Connect can allow clients to skip consent and make consent confirmation optional so as not to disrupt their online experience.
Perform the following steps to configure the OAuth 2.0 service and an OAuth 2.0 client to skip consent:
Log in to the AM console with an administrative user. For example,
amAdmin.Configure the OAuth 2.0 provider to allow clients to skip consent:
Navigate to Realms > Realm Name > Services > OAuth 2.0 provider > Consent.
Enable Allow Clients to Skip Consent.
Click Save Changes.
Configure the OAuth 2.0 client to skip consent:
Navigate to Realms > Realm Name > Applications > OAuth 2.0 > Client Name > Advanced.
Enable Implied consent.
Save your changes.
AM will now treat the requests from this client as if the resource owner/end user has already consented, and will not display consent pages during the flow.