Skip to content

Commit 40f0871

Browse files
author
sampadawagde
committed
JAVA-1132: Main README changes to accommodate module renaming
1 parent 991c2e6 commit 40f0871

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Diff for: README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ mvn clean install
1818
This project contains a number of modules, here is a quick description of what each module contains:
1919
- `oauth-rest` - Authorization Server (Keycloak), Resource Server and Angular App based on the new Spring Security 5 stack
2020
- `oauth-jwt` - Authorization Server (Keycloak), Resource Server and Angular App based on the new Spring Security 5 stack, focused on JWT support
21-
- `oauth-jws-jwk` - Authorization Server and Resource Server for JWS + JWK in a Spring Security OAuth2 Application
21+
- `oauth-jws-jwk-legacy` - Authorization Server and Resource Server for JWS + JWK in a Spring Security OAuth2 Application
2222
- `oauth-legacy` - Authorization Server, Resource Server, Angular and AngularJS Apps for legacy Spring Security OAuth2
2323

2424

@@ -63,7 +63,7 @@ npm start
6363
## Using the JS-only SPA OAuth Client
6464
The main purpose of these projects are to analyze how OAuth should be carried out on Javascript-only Single-Page-Applications, using the authorization_code flow with PKCE.
6565

66-
The *SPA/clients-js-only-react* project includes a very simple Spring Boot Application serving a couple of separate Single-Page-Applications developed in React.
66+
The *clients-SPA-legacy/clients-js-only-react-legacy* project includes a very simple Spring Boot Application serving a couple of separate Single-Page-Applications developed in React.
6767

6868
It includes two pages:
6969
* a 'Step-By-Step' guide, where we analyze explicitly each step that we need to carry out to obtain an access token and request a secured resource
@@ -78,7 +78,7 @@ After running the Spring Boot Application (a simple *mvn spring-boot:run* comman
7878
When prompted the login form, we might need to create a user for our Application first.
7979

8080
### The 'Real-Case' OAuth Client with PKCE page
81-
To use all the features contained in the *http://localhost:8080/pkce-realcase/index.html* page, we'll need to first start the resource server (SPA/oauth-resource-server-auth0).
81+
To use all the features contained in the *http://localhost:8080/pkce-realcase/index.html* page, we'll need to first start the resource server (clients-SPA-legacy/oauth-resource-server-auth0-legacy).
8282

8383
In this page, we can:
8484
* List the resources in our resource server (public, no permissions needed)

0 commit comments

Comments
 (0)