Skip to content

[Security][Guard] Added a picture for Guard Authenticator #7280

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

Closed

Conversation

a-ast
Copy link
Contributor

@a-ast a-ast commented Dec 20, 2016

This illustration shows how GuardAuthenticationListener calls methods of Guard Authenticator.

@ogizanagi
Copy link
Contributor

ogizanagi commented Dec 20, 2016

Looks great!

Beware that returning null from GuardAuthenticatorInterface::getCredentials() will try other guard authenticators before returning a response in case of multiple guards authenticators. Thus, authentication is skipped, but only for this authenticator.

@a-ast
Copy link
Contributor Author

a-ast commented Dec 20, 2016

You are right @ogizanagi, but it is always a big question: either to put all details to a picture or keep it simpler.

Copy link
Member

@wouterj wouterj left a comment

Choose a reason for hiding this comment

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

Love it! 👍

@xabbuh
Copy link
Member

xabbuh commented May 17, 2017

Thank you for this really beautiful improvement @a-ast!

xabbuh added a commit that referenced this pull request May 17, 2017
… (a-ast)

This PR was submitted for the master branch but it was merged into the 2.8 branch instead (closes #7280).

Discussion
----------

[Security][Guard] Added a picture for Guard Authenticator

This illustration shows how GuardAuthenticationListener calls methods of Guard Authenticator.

Commits
-------

ed0e6da Added the picture that shows how GuardAuthenticationListener calls Authentication Guard methods.
@xabbuh xabbuh closed this May 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants