Add SPA sample using Backend For Frontend and Spring Cloud Gateway #1816
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgrandja
force-pushed
the
spa-bff-sample
branch
from
56da18b to
82450c1
Compare
|
@jgrandja Hi, I read the code of spa-client and I saw that authorizeMessages() is called once for each request to /messages. Is this necessary? |
|
why use spring-cloud-gateway-mvc not spring-cloud-gateway, would add samples with spring-cloud-gateway ? |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This SPA sample provides a reference implementation of the Backend For Frontend (BFF) application architecture pattern.
The spa-client is the frontend SPA implemented with Angular and the backend-for-spa-client is the backend application.
The backend-for-spa-client uses Spring Cloud Gateway to route
/userinfo(UserInfo Endpoint) requests to demo-authorizationserver and/messagesrequests to messages-resource.The backend-for-spa-client performs the authorization flows and stores the access tokens.
The spa-client is never exposed the access tokens and directly communicates with the backend-for-spa-client via an authenticated session cookie.
Related gh-297, gh-564