kamagra how much to take

ADFS Not Resolving Active Directory Security Groups In SharePoint

I ran into this issue really recently working at a client with a new, pretty basic ADFS environment that was acting as the identity provider, through an ADFS proxy server relay. I couldn’t wrap my head around why it wasn’t working, the groups themselves were resolving correctly, and even showing up in the identity data sources in the people picker. However, members of the AD securitygroup, (NOT the SharePoint group) were still being denied access to the SharePoint site.

To fix this issue follow these steps:

    1. Open the federation server box.
    2. Open the ADFS management console.
    3. Edit the claim rules for the relaying party trust
    4. Select the tab Issuance Transform Rules
    5. Edit the Send LDAP Attributes as Claims
      1. This should have:
      2. Claim Rule Name : Pass-through LDAP Claims
      3. Attribute Store : Active Directory
      4. Set: Token Groups unqualified names (Don’t Use: Token Groups – Qualified by domain name) | Outgoing ClaimType: Role
      5. Set: User-Principal-Name | Outgoing Claim Type : UPN
    6. Open the SharePoint management shell, run the following PowerShell script to create the issuer. If you have an issuer already made, remove it or execute the coordinating update commands. Make sure you replace the $certPath, $realm, and any of the string literals within $ap.
  1. $certPath = your certification path
  2. $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2("$certPath")
  3. $map1 = New-SPClaimTypeMapping "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingClaimTypeDisplayName "EmailAddress" -SameAsIncoming
  4. $map2 = New-SPClaimTypeMapping "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname" -IncomingClaimTypeDisplayName "Login" –SameAsIncoming
  5. $map3 = New-SPClaimTypeMapping "http://schemas.microsoft.com/ws/2008/06/identity/claims/role" -IncomingClaimTypeDisplayName "Role" –SameAsIncoming
  6. $map4 = New-SPClaimTypeMapping "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn" -IncomingClaimTypeDisplayName "Account ID" –SameAsIncoming
  7. $realm = "urn:" + $env:ComputerName + ":adfs"
  8. $signinurl = "https://yoursigninurl"
  9. $ap = New-SPTrustedIdentityTokenIssuer -Name "ADFS" -Description ADFS 2.0 -Realm $realm -ImportTrustCertificate $cert -ClaimsMappings $map1, $map2, $map3, $map4 -SignInUrl $signinurl -IdentifierClaim $map1.InputClaimType

If you are curious about the way to update, rather than create a new issuer, you can use the following. In the above, you may or may not need all those assertion mappings depending on how your trusted relay issuance rule setup:

  1. $issuer = Get-SPTrustedIdentityTokenIssuer
  2. $issuer.ClaimTypes.Add("http://schemas.microsoft.com/ws/2008/06/identity/claims/role")
  3. $map=New-SPClaimTypeMapping "http://schemas.microsoft.com/ws/2008/06/identity/claims/role" -IncomingClaimTypeDisplayName "Role" –SameAsIncoming
  4. $issuer.AddClaimTypeInformation($map)
  5. $issuer.Update()

Now you HAVE to apply KB hotfix 2536591 located here: http://support.microsoft.com/kb/2536591/en-us

Boom! Groups will work.

Share

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>