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
The OAuthV2 Apigee policy supports storing custom attributes with the authorization code generation. These attributes are then transferred to the corresponding access token and are available during access token verification.
This functionality is not supported currently by the Volos OAuth2 library with the Apigee implementation when used remotely. I could add custom attributes only when generating the token, not the code.
Here is how the code generation function looks like:
There is no support for the "attributes" parameter which is present in the token generation function.
Even if I add "attributes" there and they are sent to the "apigee-remote-proxy" endpoint, it seems that the "apigee-access" library doesn't support this as well.
Am I doing something wrong or this is really not supported?
The text was updated successfully, but these errors were encountered:
The OAuthV2 Apigee policy supports storing custom attributes with the authorization code generation. These attributes are then transferred to the corresponding access token and are available during access token verification.
This functionality is not supported currently by the Volos OAuth2 library with the Apigee implementation when used remotely. I could add custom attributes only when generating the token, not the code.
Here is how the code generation function looks like:
There is no support for the "attributes" parameter which is present in the token generation function.
Even if I add "attributes" there and they are sent to the "apigee-remote-proxy" endpoint, it seems that the "apigee-access" library doesn't support this as well.
Am I doing something wrong or this is really not supported?
The text was updated successfully, but these errors were encountered: