Skip to content

Conversation

@mpbalmeida
Copy link
Contributor

Check user requestType paramater before apply default responseType. So the user can define the behavior.

Closes: #385
See: #385

Check user requestType paramater before apply default responseType. So the user can define the behavior.

Closes: manfredsteyer#385
See: manfredsteyer#385
@jeroenheijmans
Copy link
Collaborator

The changes look backwards compatible to me, no existing implementations would be broken AFAICT.

Out of curiosity I read through 8.4 from RFC 6749 which seems to be about this part of OAuth2. I had never known that there could even be whole other types of response_type values. So the changes all seem good to me.

One remark about the proposed PR though: it might be good to add documentation to responseType on the AuthConfig class. I'm not sure how the docs are generated, but given the current state I think those are generated from the block-comments too.

@glambkin
Copy link

@mpbalmeida Great work, I could really do with this change too. I agree with @jeroenheijmans it would be good to add the doc to the AuthConfig class.

I have also raised a support issue with AWS, I may be wrong, but I don't think they are fully compliant with the spec.

Copy link

@glambkin glambkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a doc to the AuthConfig responseType and remove the whitespace commits?

Copy link

@glambkin glambkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

accidental comment

this.responseType = this.config.responseType;
} else {
this.responseType = 'token';
if (this.oidc && this.requestAccessToken) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could be else if, too, right? That would simplify this if/else/else if complexity, I think :)

@FlorianSW
Copy link

One comment, otherwise I would love to see this merged and released :)

@manfredsteyer
Copy link
Owner

Thx

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

Successfully merging this pull request may close these issues.

5 participants