[jbosstools-issues] [JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
Andre Dietisheim (JIRA)
jira-events at lists.jboss.org
Mon Nov 4 07:58:01 EST 2013
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840890#comment-12840890 ]
Andre Dietisheim commented on JBIDE-15847:
------------------------------------------
The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user at redhat.com>*.
According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On*
{quote}
01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers?
(01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this
(01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments
(01:44:28 PM) bleanhar: it's now the default
(01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config?
(01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided
{quote}
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list