From fc35be81cde1df3c9dba9ada282dd7614a6a2b20 Mon Sep 17 00:00:00 2001 From: Stian Thorgersen Date: Fri, 10 Jun 2016 09:20:13 +0200 Subject: [PATCH] Fix --- topics/identity-broker/overview.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/identity-broker/overview.adoc b/topics/identity-broker/overview.adoc index 9669e3040e..a4123d8059 100644 --- a/topics/identity-broker/overview.adoc +++ b/topics/identity-broker/overview.adoc @@ -44,4 +44,4 @@ NOTE: Different protocols may require different authentication flows. As you may notice, at the end of the authentication process {{book.project.name}} will always issue its own token to client applications. What this means is that client applications are completely decoupled from external identity providers. They don't need to know which protocol (eg.: SAML, OpenID Connect, OAuth, etc) was used or how the user's identity was validated. -They only need to know about {{book.project.name}} ! +They only need to know about {{book.project.name}}.