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

Update topics/overview/supported-protocols.adoc

Browse source
This commit is contained in:
Stian Thorgersen 2016-06-10 06:40:04 +02:00
parent adbfed0f9a
commit 2e1d421159
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
topics/overview/supported-protocols.adoc
View file

@ -32,7 +32,7 @@ In {{book.project.name}} SAML serves two types of use cases: browser application
There is really two types of use cases when using SAML. The first is an application that asks the {{book.project.name}} server to authenticate There is really two types of use cases when using SAML. The first is an application that asks the {{book.project.name}} server to authenticate
a user for them. After a successful login, the application will receive an XML document that contains a user for them. After a successful login, the application will receive an XML document that contains
something called a SAML assertion that specify various attributes about the user. This XML document is digitally signed by something called a SAML assertion that specifies various attributes about the user. This XML document is digitally signed by
the realm and contains access information (like user role mappings) that the application can use to determine what resources the user the realm and contains access information (like user role mappings) that the application can use to determine what resources the user
is allowed to access on the application. is allowed to access on the application.