IDPv3 Attribute Resolver help
Cantor, Scott
cantor.2 at osu.edu
Tue Nov 8 08:50:11 EST 2016
On 11/8/16 7:05 AM, Tim Williams wrote:
>
> eg, the document:
>
> https://wiki.shibboleth.net/confluence/display/IDP30/StartTLSAuthenticationCredential
>
> Only tells me how to configure a certificate file I already have so that
> Shibboleth can use it, but it doesn't tell me what I have to do at the
> AD end to obtain/configure the certificate so that AD knows about it as
> well.
That's for TLS authentication *to* AD, not the way to configure the IdP
to trust the AD's cert, but it appears you don't have TLS here anyway.
> Hmm, I originally had DEBUG logging turned on and I was advised in an
> earlier reply on this list to turn it off because it was too noisy and
> didn't provide much useful information for non-developers.
That depends on what the issue is.
> Both are set to false and I'm using ldap:// in the URL, but I'm still
> getting a fail when the LDAP resolver is set up telling me the
> certificate path is invalid:
If you leave the properties set up to rely on a provided certificate for
trust, and don't provide one, it fails. If you want ldap:// and there is
no certificate, set the idp.authn.LDAP.sslConfig property to jvmTrust, I
think, that should bypass the need to give it anything, at least for
authentication.
On the attribute resolver side, you should just be able to *not* provide
any trust material in the LDAP connector.
-- Scott
More information about the users
mailing list