libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

[KEYCLOAK-14339] demo-template readme with syntax error

Browse source 
change step 10 and 11 to have consistent syntax with the rest
This commit is contained in:
mevech 2020-05-30 15:18:00 +02:00 committed by Stian Thorgersen
parent b95ca30ec2
commit 75a5452805
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
examples/demo-template/README.md
View file

@ -200,7 +200,7 @@ If you are already logged in, you will not be asked for a username and password,
an oauth grant page. This page asks you if you want to grant certain permissions to the third-part app. an oauth grant page. This page asks you if you want to grant certain permissions to the third-part app.
Step 10: Service Account Example Step 10: Service Account Example
================================ ----------------------------------
An example for retrieve service account dedicated to the Client Application itself (not to any user). An example for retrieve service account dedicated to the Client Application itself (not to any user).
[http://localhost:8080/service-account-portal](http://localhost:8080/service-account-portal) [http://localhost:8080/service-account-portal](http://localhost:8080/service-account-portal)
@ -208,7 +208,7 @@ An example for retrieve service account dedicated to the Client Application itse
Client authentication is done with OAuth2 Client Credentials Grant in out-of-bound request (Not Keycloak login screen displayed) . Client authentication is done with OAuth2 Client Credentials Grant in out-of-bound request (Not Keycloak login screen displayed) .
Step 11: Offline Access Example Step 11: Offline Access Example
=============================== ----------------------------------
An example for retrieve offline token, which is then saved to the database and can be used by application anytime later. Offline token An example for retrieve offline token, which is then saved to the database and can be used by application anytime later. Offline token
is valid even if user is already logged out from SSO. Server restart also won't invalidate offline token. Offline token can be revoked by the user in is valid even if user is already logged out from SSO. Server restart also won't invalidate offline token. Offline token can be revoked by the user in
account management or by admin in admin console. account management or by admin in admin console.