Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Windows MSI installer and idp.attribute.resolver.LDAP.searchFilter=

Description

Discussed in this thread - http://shibboleth.1660669.n2.nabble.com/Questions-about-making-Shibboleth-IdP-Windows-Installer-easier-to-deploy-searchFilter-useStartTLS-Ho-td7633230.html

Assuming Shibboleth IdP Windows Installer users are going to go the route of using Active Directory (AD) as the LDAP source for their Shibboleth IdP, then it would be useful if idp.attribute.resolver.LDAP.searchFilter= used sAMAccountName rather than uid. This appears to already happened for idp.authn.LDAP.userFilter= already.

Proposing an improvement to replace this;

idp.attribute.resolver.LDAP.searchFilter= (uid=$resolutionContext.principal)

with this as part of either the Windows MSI installer, or other Shibboleth installer (The discussion with Rod and Scott also mentioned whether this should be considered in a cross-platform context.)

{{
idp.attribute.resolver.LDAP.searchFilter=(sAMAccountName=$resolutionContext.principal)}}

Thanks,

  • Jon Agland, UK federation team, Jisc

Environment

None

Activity

Show:

Rod WiddowsonApril 29, 2018 at 10:27 AM

Made the obvious fix.

The more complicated question (about making AD configuration orthogonal to Wi ndows Installation) will wait for V4

Rod WiddowsonAugust 15, 2017 at 4:41 PM

I think I want this to be V4 and part of a bigger picture. But I'm not there yet,,,

Fixed

Details

Assignee

Reporter

Components

Fix versions

Created May 19, 2017 at 10:56 AM
Updated June 22, 2021 at 11:04 PM
Resolved April 29, 2018 at 10:27 AM