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

Fix broken links in Authentication SPI chapter (#7)

Browse source
This commit is contained in:
Marek Posolda 2016-06-08 09:08:19 +02:00 committed by Stian Thorgersen
parent ea0ef24dd3
commit dc6c386b40
2 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
book.json
View file

@ -18,7 +18,7 @@
"version": "10"
},
"adminguide": {
"name": "Keycloak Administration Guide",
"name": "Server Administration Guide",
"link": "https://keycloak.gitbooks.io/server-adminstration-guide/content/"
},
"clientguide": {

15
topics/auth-spi.adoc
View file

@ -373,7 +373,7 @@ getReferenceCategory() is just a category the Authenticator belongs to.
==== Adding Authenticator Form
Keycloak comes with a Freemarker <<_themes,theme and template engine>>.
Keycloak comes with a Freemarker <<fake/../themes.adoc#_themes,theme and template engine>>.
The createForm() method you called within authenticate() of your Authenticator class, builds an HTML page from a file within your login theme: secret-question.ftl.
This file should be placed in the login theme with all the other .ftl files you see for login.
@ -754,14 +754,19 @@ In other words, add your custom authenticator after the "Send Reset Email" authe
=== Modifying First Broker Login Flow
First Broker Login flow is used during first login with some identity provider.
Term `First Login` means that there is not yet existing Keycloak account linked with the particular authenticated identity provider account.
More details about this flow are in the <<_identity_broker_first_login,Identity provider chapter>>.
Term `First Login` means that there is not yet existing {{book.project.name}} account linked with the particular authenticated identity provider account.
More details about this flow are in the `Identity Brokering` chapter in link:{{book.adminguide.link}}[{{book.adminguide.name}}] .
[[_client_authentication]]
=== Authentication of clients
Keycloak actually supports pluggable authentication for http://openid.net/specs/openid-connect-core-1_0.html[OpenID Connect] client applications.
Authentication of client (application) is used under the hood by the <<_adapter_config,Keycloak adapter>> during sending any backchannel requests to the Keycloak server (like the request for exchange code to access token after successful authentication or request to refresh token). But the client authentication can be also used directly by you during <<_direct_access_grants,Direct Access grants>> or during <<_service_accounts,Service account>> authentication.
{{book.project.name}} actually supports pluggable authentication for http://openid.net/specs/openid-connect-core-1_0.html[OpenID Connect] client applications.
Authentication of client (application) is used under the hood by the {{book.project.name}} adapter during sending any backchannel requests
to the {{book.project.name}} server (like the request for exchange code to access token after successful authentication or request to refresh token).
But the client authentication can be also used directly by you during `Direct Access grants` (represented by OAuth2 `Resource Owner Password Credentials Flow`)
or during `Service account` authentication (represented by OAuth2 `Client Credentials Flow`).
See link:{{book.clientguide.link}}[{{book.clientguide.name}}] for more details about {{book.project.name}} adapter and OAuth2 flows.
==== Default implementations