LDAP AUTHENTICATION FAILED UPGRADE SHIBBOLETH V2.3 TO V3.3

Wed Jun 27 07:24:31 EDT 2018

I didn't do an upgrade I did a fresh install.
I am using the V2.3 files to compare against what I have in the ldap.properties file.

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Rod Widdowson
Sent: Wednesday, June 27, 2018 3:48 AM
To: 'Shib Users' <users at shibboleth.net>
Subject: RE: LDAP AUTHENTICATION FAILED UPGRADE SHIBBOLETH V2.3 TO V3.3

Some brief observations - I have forgotten much of what I ever knew about V2 to V3 upgrades.

> Relying-party.xml
> <resolver:DataConnector id="myAD" xsi:type="LDAPDirectory" xmlns="urn:mace:shibboleth:2.0:resolver:dc"

That doesn't look right.  That is a line from the attribute resolver.
Further this doesn't have anything to do with attribute resolution (which you can and should test right now using aacli).

This is to do with authentication (login).  IIRC the only authentication was via jaas - there was no native LDAP authentication.

So, if you did the recommended thing of letting the install do the upgrade you probably need to be poking at your JAAS configuration.

> # LDAP authentication configuration, see authn/ldap-authn-config.xml # 
> Note, this doesn't apply to the use of JAAS

Start by reviewing [1] if you are not working from it.

[1] https://wiki.shibboleth.net/confluence/display/IDP30/UpgradingFromV2#UpgradingFromV2-Authentication

R

--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net