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

Knotx/knotx-example-project#58 refactor OAuth2 security #67

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Mateusz512
Copy link
Contributor

Refactor OAuth2 tutorial to use OOTB Vert.x implementation of OAuth2 flow

Description

The routing logic has been moved to correct security logic and now uses OOTB Vert.x stuff.

Motivation and Context

In previous approach, the OAuth2 flow was mixed with business logic.

Screenshots (if appropriate)

Upgrade notes (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

I hereby agree to the terms of the Knot.x Contributor License Agreement.

mateusz.hinc added 2 commits January 29, 2020 16:38
…urity-example-oauth2

# Conflicts:
#	api-gateway/security/knotx/conf/openapi.yaml
#	api-gateway/security/knotx/conf/routes/operations.conf

public class OAuth2HelloHandlerFactory implements AuthHandlerFactory {

private OAuth2AuthHandler oAuth2AuthHandler;

Choose a reason for hiding this comment

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

What if configuration contains two entries for this OAuthHelloHandlerFactory?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

in io.knotx.server.SecurityProvider reference to factories is a map<factoryName, factory reference>, so it will be unique anyway

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.

2 participants