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

Update OAuthHelper to include new method to support SAML grant type flow #290

Closed
miklish opened this Issue Sep 12, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@miklish
Collaborator

miklish commented Sep 12, 2018

Support must be added to support the new SAML grant type OAuth flow.

A getTokenSAMLFlow() method will be added to OAuthHelper to aid with this.

Light Router must accept a JWT and a SAML token in it's header under the header keys assertion (for SAML) and client_assertion (for JWT).

It must then POST these tokens* to an OAuth authorization server (encoded as x-www-for-urlencoded) and receive a JWT in response, and then set this new Bearer {JWT} in its header under the Authorization key before service lookup and forwarding the request.

    • In addition to the tow tokens, the authorization server expects the following additional values in x-www-form-urlencoded payload:
  • grant_type: urn:ietf:params:oauth:grant-type:saml2-bearer
  • scope: {blank separated list of OAuth scopes}*
  • client_assertion_type: urn:ietf:params:oauth:client-assertion-type:jwt-bearer

* Note that the scope key/value pair is optional.

@miklish

This comment has been minimized.

Collaborator

miklish commented Sep 12, 2018

This is currently being worked on by dguncb. I don't have access to assign issues though, and dguncb doesn't have access to be assigned. Can you set us up Steve? Thanks

@stevehu

This comment has been minimized.

Contributor

stevehu commented Sep 12, 2018

@miklish @dguncb I have added you the the member list. Please accept the invitation and you should have the access. Thanks.

@stevehu

This comment has been minimized.

Contributor

stevehu commented Sep 12, 2018

Is there a middleware handler who is responsible for intercepting the headers and calling the OAuth 2.0 provider to exchange the token?

@miklish

This comment has been minimized.

Collaborator

miklish commented Sep 12, 2018

@miklish

This comment has been minimized.

Collaborator

miklish commented Sep 12, 2018

@stevehu

This comment has been minimized.

Contributor

stevehu commented Sep 24, 2018

This has been resolved by the PR #292

@stevehu stevehu closed this Sep 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment