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
I'm using the AppAuth library to make the Dynamic Client Registration. It follows the OIDC specs to the letter (https://openid.net/specs/openid-connect-registration-1_0.html#ClientRegistration) without much flexibility to change the process.
When calling /SAAS/auth/device/register, it triggers a POST with all parameters in the body (as specified in the RFC) and not as a query parameter. I got back from VIDM an HTTP 400 error with the following message: Empty user_device parameter. Even if I'm sending it on the post body.
If I send as a query parameter, it works. However I cannot make AppAuth do it, since it only follows the standard.
So I would like to know if it's possible to support sending the arguments as post body to conform to the RFCs.
The text was updated successfully, but these errors were encountered:
I'm using the AppAuth library to make the Dynamic Client Registration. It follows the OIDC specs to the letter (https://openid.net/specs/openid-connect-registration-1_0.html#ClientRegistration) without much flexibility to change the process.
When calling /SAAS/auth/device/register, it triggers a POST with all parameters in the body (as specified in the RFC) and not as a query parameter. I got back from VIDM an HTTP 400 error with the following message: Empty user_device parameter. Even if I'm sending it on the post body.
If I send as a query parameter, it works. However I cannot make AppAuth do it, since it only follows the standard.
So I would like to know if it's possible to support sending the arguments as post body to conform to the RFCs.
The text was updated successfully, but these errors were encountered: