You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to OIDC core when request object is used by value or by reference, the OAuth parameters response_type & scope are required.
BUT the FAPI conformance test suite execute some tests where the response_type and scope parameters are present into the request object passed by reference but missing from the query parameters... these tests shall pass even if the OIDC core specification consider it as invalid...
The reason of this inconsistency comes from the OAuth JAR (currently in draft n°34) that requires only the client_id and the request or request_uri parameters because the other ones MUST be present into the request object...
The text was updated successfully, but these errors were encountered:
leleueri
changed the title
[FAPI][PAR] scope & response_type are optional in OAuth parameters
[FAPI] scope & response_type are optional in OAuth parameters
Aug 9, 2021
tcompiegne
changed the title
[FAPI] scope & response_type are optional in OAuth parameters
[fapi] scope & response_type are optional in OAuth parameters
Aug 13, 2021
leleueri
added a commit
to gravitee-io/gravitee-access-management
that referenced
this issue
Sep 1, 2021
According to OIDC core when request object is used by value or by reference, the OAuth parameters
response_type
&scope
are required.BUT the FAPI conformance test suite execute some tests where the
response_type
andscope
parameters are present into the request object passed by reference but missing from the query parameters... these tests shall pass even if the OIDC core specification consider it as invalid...The reason of this inconsistency comes from the OAuth JAR (currently in draft n°34) that requires only the
client_id
and therequest
orrequest_uri
parameters because the other ones MUST be present into the request object...The text was updated successfully, but these errors were encountered: