feat: Add support for configurable prompt type for Google connector #3475
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.
Overview
Add support for configurable prompt type for Google Connector. Reference #3450
What this PR does / why we need it
prompt
parameter in login URL generated by Google connectorSpecial notes for your reviewer
Ref #3450
The original ask was to avoid the user experience of consent screen every time authentication flow goes through
dex
into Google by skippingprompt=consent
flag. As per OIDC specification, there is no valid value forprompt
param to achieve this. So this PR just allows the ability to set the value ofprompt
parameter through configuration. Setting an explicit""
(empty) value for prompt should be functionally equivalent for skipping it for Google connector