Purpose of Request Object in OpenID Connect
This enables sending authentication request parameters in a self-contained JWT instead of plain request parameters. Request Object can be specified to the authorization server either by value or by reference.
- Here the requested scope is considered as 'openid email' as the scope value of the request object is declared. So the server will ignore the scope value which is associated with the authorization request and considers the requested scope as 'openid email'
- It considers the claims "given_name" and "email" which are marked as 'essential:true' for 'userinfo' member. Even if they are not mapped with the openid or address scope in the registry, if these claims are requested claims, then 'given_name' and 'email' will be returned from the Userinfo endpoint. In a nutshell, the claims which are marked as 'essential: true' only get controlled by the requested claims and ignore the requested scopes. If the server cannot provide those essential claims, there will not be any failure or error message returning from the server.
- The claims like "nickname" it will act as a default claim and will be controlled by both requested scopes and the requested claims.
- If the server cannot provide the requested essential claims, the server will return null for the specific claim and the flow will not break.
This behavior is common to the id token as well
You can try out the sample listed in Passing OIDC Authentication Request Parameters in a Request Object page to see how request objects work in IS.
If the Request Object is a nested JWT, which is signed and encrypted, then the payload (Cipher Text) of the Request Object is a signed JWT. So the server will decrypt the JWE first and then check the payload for signature validation.
All the validations and the request object builder are extensible so that a third party user can build the request object and do any validations in their own way. At the moment, Identity Server does not have a default implementation for request_uri parameter and instead, it extracts the request_uri parameter from the request object and pass it.
The following configuration changes should be done in
$IS_HOME/repository/conf/identity/identity.xmlwhen writing extension points for this feature.
<OpenIDConnect> <RequestObjectBuilders> <RequestObjectBuilder> <Type>request_param_value_builder</Type> <ClassName>org.wso2.carbon.identity.openidconnect.RequestParamRequestObjectBuilder</ClassName> </RequestObjectBuilder> </RequestObjectBuilders> <RequestObjectValidator>org.wso2.carbon.identity.openidconnect.RequestObjectValidatorImpl</RequestObjectValidator> </OpenIDConnect>
If the configuration is not present, the default classes will be executed.
Please note that Identity Server 5.5.0 does not have a default implementation for request_uri parameter.
If you implement a