2:29 p.m.
Hello,
I am trying to get ldap to work and it seems the query in picketlink's
LDAPIdentityStore.java on line 186 uses id or uid to find the user in an
Active Directory. Our Active Directory stores the username as the property
sAMAccountName. I believe this prevents keycloak's new ldap integration
from working. Am I missing something?
1:35 a.m.
We already seem to have other person with very similar usecase like you.
I am working on it and will let you know.
Marek
On 19.6.2014 20:29, Dean Peterson wrote:
Hello,
I am trying to get ldap to work and it seems the query in picketlink's
LDAPIdentityStore.java on line 186 uses id or uid to find the user in
an Active Directory. Our Active Directory stores the username as the
property sAMAccountName. I believe this prevents keycloak's new ldap
integration from working. Am I missing something?
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
8:19 a.m.
Marek,
BTW, we need a more user friendly interface for ldap setup than passing
a system property on startup.
On 6/19/2014 2:29 PM, Dean Peterson wrote:
Hello,
I am trying to get ldap to work and it seems the query in picketlink's
LDAPIdentityStore.java on line 186 uses id or uid to find the user in an
Active Directory. Our Active Directory stores the username as the
property sAMAccountName. I believe this prevents keycloak's new ldap
integration from working. Am I missing something?
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11:40 a.m.
That sounds great, thanks!
On Fri, Jun 20, 2014 at 12:35 AM, Marek Posolda <mposolda(a)redhat.com> wrote:
We already seem to have other person with very similar usecase like
you.
I am working on it and will let you know.
Marek
On 19.6.2014 20:29, Dean Peterson wrote:
Hello,
I am trying to get ldap to work and it seems the query in picketlink's
LDAPIdentityStore.java on line 186 uses id or uid to find the user in an
Active Directory. Our Active Directory stores the username as the property
sAMAccountName. I believe this prevents keycloak's new ldap integration
from working. Am I missing something?
_______________________________________________
keycloak-user mailing
listkeycloak-user@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-user
4:51 a.m.
Hi,
ATM There is fix in latest Keycloak master . Among other improvements,
you can now configure in admin console the name of LDAP attribute, which
is used as username in Keycloak. So for AD, you can select
"sAMAccountName" . I believe that this will help to have things working
in your environment. Please let me know if it helps.
Thanks,
Marek
On 20.6.2014 17:40, Dean Peterson wrote:
That sounds great, thanks!
On Fri, Jun 20, 2014 at 12:35 AM, Marek Posolda <mposolda(a)redhat.com
<mailto:mposolda@redhat.com>> wrote:
We already seem to have other person with very similar usecase
like you. I am working on it and will let you know.
Marek
On 19.6.2014 20:29, Dean Peterson wrote:
> Hello,
>
> I am trying to get ldap to work and it seems the query in
> picketlink's LDAPIdentityStore.java on line 186 uses id or uid to
> find the user in an Active Directory. Our Active Directory
> stores the username as the property sAMAccountName. I believe
> this prevents keycloak's new ldap integration from working. Am I
> missing something?
>
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-user
3591
days inactive
3596
days old
4 comments
3 participants
participants (3)
-
Bill Burke -
Dean Peterson -
Marek Posolda