Skip to content
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

Updated Getting Started + KC setup scripts + renamed postman files (as some chars are illegal in windows) #34

Merged
merged 9 commits into from
Mar 4, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
11 changes: 8 additions & 3 deletions doc/GETTING_STARTED.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,11 @@ $ mvn clean install
There is docker-compose.yml in root folder which will help to run containers in docker.
Some images will be build from sources, some fetched prebuild from docker hub.

UI componet should be build before docker images created.
UI component should be built before docker images were created.
```
$ cd online-banking-demo-ui && npm ci && npm run build && cd ..
```
After UI build completed start docker compose.
After UI build completes please start docker compose.
```
$ docker-compose up
```
Expand Down Expand Up @@ -62,6 +62,11 @@ After keycloak starts and listens on port `8081` you may run keycloak scripts th
$ cd scripts/keycloak-dev
$ ./init-realm-and-client.sh
```
You should see new realm, client and user created in your keycloak.

Please note clients should be created with ``Access Type`` bearer-only and there should be tab named Credentials where you can get client secret, used in next step. ![client secret](images/keycloakClientSecret.png)

In case tab Credentials are not visible, please toggle ``Access Type`` setting on tab ``Settings`` (change to public, save and change back to bearer-only).

The user with username `admin` and password `admin123` will be used for keycloak administration then.
The user with username `aspsp` and password `zzz` will be used for accessing the aspsp-mock-server api then.
Expand Down Expand Up @@ -122,7 +127,7 @@ For initial startup and testing purposes one can use the connector to the aforem
To start the XS2A with ASPSP-Mock-Connector do:
```bash
$ cd spi-mock
$ mvn -dKEYCLOAK_CREDENTIALS_SECRET="xyz" spring-boot:run
$ mvn -DKEYCLOAK_CREDENTIALS_SECRET="xyz" spring-boot:run
```
Where `xyz` - a client-secret generated by keycloak for `xs2a-impl` client.

Expand Down
Binary file added doc/images/keycloakClientSecret.PNG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions scripts/keycloak-dev/init-realm-and-client.sh
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@ echo 'create xs2a realm'
sh add-realm.sh http://localhost:8081 xs2a admin admin123

echo 'create client xs2a-impl'
sh add-realm-client.sh http://localhost:8081 xs2a xs2a-impl false admin admin123
sh add-realm-client.sh http://localhost:8081 xs2a xs2a-impl true admin admin123

echo 'create client aspsp-mock'
sh add-realm-client.sh http://localhost:8081 xs2a aspsp-mock false admin admin123
sh add-realm-client.sh http://localhost:8081 xs2a aspsp-mock true admin admin123

echo 'create admin role'
roleId=$(sh add-realm-role.sh http://localhost:8081 xs2a admin admin123 admin)
Expand Down
2 changes: 1 addition & 1 deletion scripts/tests/postman/.gitignore
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
*.postman_environment.json
!Local ENV.postman_environment.json
!Local_ENV.postman_environment.json