[
https://issues.jboss.org/browse/RTGOV-622?page=com.atlassian.jira.plugin....
]
Gary Brown updated RTGOV-622:
-----------------------------
Description:
Moved to KeyCloak SSO in RTGOV-609. However now the security context
getUserPrincipal().getName() returns a UID instead of the username.
This causes problems when needing to identify the actual user (e.g. assigning a situation
etc).
The KeyCloak issue is being discussed here:
http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html
was:
Moved to KeyCloak SSO in RTGOV-609. However now the security context
getUserPrincipal().getName() returns a UID instead of the username.
This causes problems when needing to identify the actual user (e.g. assigning a situation
etc).
Keycloak returning UID from security context user principal name
----------------------------------------------------------------
Key: RTGOV-622
URL:
https://issues.jboss.org/browse/RTGOV-622
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
Moved to KeyCloak SSO in RTGOV-609. However now the security context
getUserPrincipal().getName() returns a UID instead of the username.
This causes problems when needing to identify the actual user (e.g. assigning a situation
etc).
The KeyCloak issue is being discussed here:
http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)