I have a similar question as in Format for 'openid connect authorize parameters' field.
Our Auth0 setup requires to add connection=123 to the authorize endpoint. I tried several combinations of openid connect authorize parameters without success.
So either please give me a working example or fix the bug - I have the impression that the given parameters are not routed through to the authorize request at all.
Looking at the code it looks like it needs to be in request params.
Try using chrome dev tools, track all HTTP requests, are you certain this allow listed param is in the request params? This is just used to allow list stuff, not to hardcode a value.
If you need to hardcode a value a new feature would need to be built.
I don’t get it. The parameters are not added at all…
Happened to me on one occasion, adding the parameter directly in the authorize_url seems to do the trick 
And how are you supposed to do this? The plugin only takes the discovery document:
plugins:
openid_connect_enabled:
default: false
openid_connect_discovery_document:
default: ""
openid_connect_client_id:
default: ""
openid_connect_client_secret:
default: ""
openid_connect_rp_initiated_logout:
default: false
openid_connect_rp_initiated_logout_redirect:
default: ""
openid_connect_allow_association_change:
default: false
openid_connect_overrides_email:
default: false
openid_connect_authorize_scope:
default: "openid"
openid_connect_verbose_logging:
default: false
openid_connect_token_scope:
default: ""
openid_connect_error_redirects:
default: ""
type: list
list_type: secret
openid_connect_authorize_parameters:
default: ""
type: list
list_type: compact
openid_connect_claims:
default: ""
textarea: true
openid_connect_match_by_email:
default: true
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.