Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1175

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.0
    • Component/s: Installer, MSI Installer
    • Labels:
      None
    • Operating System:
      Windows

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rdw@iay.org.uk Rod Widdowson
              Reporter:
              g2sksi+jdomx00zgqaudqhgf5+i=@https://idp.jisc.ac.uk/idp/shibboleth g2sksi+jdomx00zgqaudqhgf5+i=@https://idp.jisc.ac.uk/idp/shibboleth
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h