fixed RHSSO-870

This commit is contained in:
Jen Malloy 2017-03-21 14:25:37 -04:00
parent 5c68ae6139
commit d08d4202ed
3 changed files with 3 additions and 6 deletions

View file

@ -206,7 +206,7 @@ realmAccess::
The realm roles associated with the token.
resourceAccess::
The resource roles assocaited with the token.
The resource roles associated with the token.
refreshToken::
The base64 encoded refresh token that can be used to retrieve a new token.

View file

@ -1,6 +1,4 @@
==== Troubleshooting
The best way to troubleshoot some problems is to turn on debugging for saml in both the client adapter and the {{book.project.name}} server.
To do this turn on debugging int the `org.keycloak.saml` package to `debug` in your log4j or other logging framework.
Turning this on allows you to see the SAML requests and response documents being sent to and from the server.
The best way to troubleshoot problems is to turn on debugging for SAML in both the client adapter and {{book.project.name}} Server. Using your logging framework, set the log level to `DEBUG` for the `org.keycloak.saml` package. Turning this on allows you to see the SAML requests and response documents being sent to and from the server.

View file

@ -2,8 +2,7 @@
===== SP PrincipalNameMapping element
This element is optional.
When creating a Java Principal object that you obtain from methods like `HttpServletRequest.getUserPrincipal()`, you can
define what name that is returned by the `Principal.getName()` method.
When creating a Java Principal object that you obtain from methods such as `HttpServletRequest.getUserPrincipal()`, you can define what name is returned by the `Principal.getName()` method.
[source,xml]
----