Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OAuth2: Setting custom attributes with authorization code generation is not supported #111

Open
ivan-novakov opened this issue Jan 25, 2017 · 0 comments

Comments

@ivan-novakov
Copy link

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:

OAuthImpl.prototype.generateAuthorizationCode = function(options, cb) {
  var r = _.pick(options,
    'clientId', 'redirectUri', 'scope', 'state'
  );
  r.responseType = 'code';
  debug('generateAuthorizationCode: %j', r);
[...]

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant