From 2e1d42115933472c81dbcae8527cdbbada761c0a Mon Sep 17 00:00:00 2001 From: Stian Thorgersen Date: Fri, 10 Jun 2016 06:40:04 +0200 Subject: [PATCH] Update topics/overview/supported-protocols.adoc --- topics/overview/supported-protocols.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/overview/supported-protocols.adoc b/topics/overview/supported-protocols.adoc index e97ba919b1..67c473d070 100644 --- a/topics/overview/supported-protocols.adoc +++ b/topics/overview/supported-protocols.adoc @@ -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 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 is allowed to access on the application.