By: Andrea Tamas user 08 Mar 2021 at 4:35 a.m. CST

2 Responses
Andrea Tamas gravatar
Hello, I am using `Gluu Server 4.2`, dockerized version on `Ubuntu 20.04.1 LTS`. The SAML authentication seems to work fine, I can login with the credentials given in `settings.py`. My problem is that I don't get the attributes in the assertion. I found the following in the `idp-process.log`: ``` 2021-03-08 10:20:20,240 - 172.27.0.1 - ERROR [net.shibboleth.idp.profile.impl.ResolveAttributes:293] - Profile Action ResolveAttributes: Error resolving attributes net.shibboleth.idp.attribute.resolver.ResolutionException: Data Connector 'siteDataConnector': Unable to execute LDAP search at net.shibboleth.idp.attribute.resolver.dc.ldap.impl.LDAPDataConnector.retrieveAttributes(LDAPDataConnector.java:225) Caused by: org.ldaptive.LdapException: LDAPException(resultCode=49 (invalid credentials), errorMessage='invalid credentials', ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb) at org.ldaptive.provider.ProviderUtils.throwOperationException(ProviderUtils.java:55) Caused by: com.unboundid.ldap.sdk.LDAPBindException: invalid credentials at com.unboundid.ldap.sdk.LDAPConnection.bind(LDAPConnection.java:2304) ``` In `settings.py` there is the password for LDAP as follows: `LDAP_PW = "Alma1!"` and I found that in the oxshibboleth container's `opt/shibboleth-idp/conf/ldap.properties` file it looks different: ``` idp.authn.LDAP.bindDNCredential = b'Alma1!' ``` After removing the extra characters manually (`idp.authn.LDAP.bindDNCredential = Alma1!`) and restarting the oxshibboleth container the error from the `idp-process.log` is gone and I get the attributes. Do I have something misconfigured? Can you advice please? Many thanks. Best regards, Andi

By Isman Firmansyah staff 08 Mar 2021 at 9:04 a.m. CST

Isman Firmansyah gravatar
Hi Andrea, Try upgrading the image to `gluufederation/oxshibboleth:4.2.3_03`.

By Michael Schwartz Account Admin 08 Mar 2021 at 9:34 a.m. CST

Michael Schwartz gravatar
It looks like a python2 - python3 bug. Good find. I'm closing it. Please re-open if it persists in the version Isman specified.