Replace Spring Security OAuth with Okta Spring Boot Starter #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE. This PR only exists to demonstrate an issue in the Okta Spring Boot Starter.
It seems like it should be possible to reduce the number of properties needed for Spring Security OAuth by simply adding the Okta Spring Boot Starter. Unfortunately, it does not work.
To reproduce the issue. Create a
~/.okta.env
file with your settings for an Okta Web app.Clone this project and checkout the
oauth
branch:Source your app settings and run each app:
You should be able to log in at http://localhost:8081 and see data from the beer-catalog-service at http://localhost:8081/good-beers.
Now, check out the
oauth-okta
branch and add your client ID and secret to~/.okta.env
.Run the following commands to restart everything with the new settings:
You'll be able to log in at http://localhost:8081, but you won't be able to access http://localhost:8081/good-beers.