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

Support for the OAuth 2.0 Implicit Grant Flow #14

Closed
DonMartin76 opened this issue Oct 4, 2016 · 2 comments
Closed

Support for the OAuth 2.0 Implicit Grant Flow #14

DonMartin76 opened this issue Oct 4, 2016 · 2 comments
Milestone

Comments

@DonMartin76
Copy link
Member

This is a requirement from Haufe:

  • In order to support client side (browser) AJAX calls to an API, wicked should support external authorization servers
  • The authorization server should be able to issue access tokens for use in pure client side apps (e.g. Angular, React type web apps)
  • To safely pass on the token to the app, the OAuth 2.0 Implicit Grant Flow should be used

This boils down to the following requirements:

  • A new auth type is added, oauth2-implicit
  • An application can be specified to support that type, in which case you can also add a redirect_uri, which is needed for the authorization server
  • Subscriptions of such apps to corresponding APIs will not trigger the creation of consumers in Kong, but will rely on the authorization server creating these/authorizing the users one by one as they login (using whatever means the authorization server requires)
  • The Kong Adapter supports a new call /oauth2/register which takes user data and returns an access token

Use Cases which can be implemented using this:

  • SAML federation (SSO federation)
  • Any other authentication federation

The authorization server can, in the SAML case, be registered as a SAML SP, and can federate the authentication to the APIs; this enables you to just register the API Portal once, and then use wicked to enable self service SSO to your SAML identity provider. This is very nifty.

@DonMartin76 DonMartin76 added this to the 1.0.0 milestone Oct 4, 2016
@DonMartin76 DonMartin76 modified the milestones: 0.10.0, 1.0.0 Oct 15, 2016
@DonMartin76
Copy link
Member Author

This will most probably land in 0.10.0 already. Progressing fine.

@DonMartin76
Copy link
Member Author

Done.

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

No branches or pull requests

1 participant