Skip to content

Fix the typo #126

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.

Sign up for GitHub

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

Merged
Buzzardo merged 1 commit into from
Jun 5, 2020
Merged

Fix the typo #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fix the typo
  • Loading branch information
@burning-croissant
burning-croissant authored Jun 5, 2020
commit 0a2bcc20dbffa0944a501c5ff8d42b3d5097974d
2 changes: 1 addition & 1 deletion custom-error/README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ To spice things up a bit, you can extend the authentication rule to reject users
You can use the GitHub API to find out more about the user, so you'll just need to plug that into the right part of the authentication process.

Fortunately, for such a simple use case, Spring Boot has provided an easy extension point:
If you declare a `@Bean` of type `OAuth2UserService`, it will be used identify the user principal.
If you declare a `@Bean` of type `OAuth2UserService`, it will be used to identify the user principal.
You can use that hook to assert the the user is in the correct organization, and throw an exception if not:

.SocialApplication.java
Expand Down