I have hit a bit of a roadblock in some recent work, and I'm not sure how to proceed.
What I've done so far:
Set up ADFS integration - users can sign in to SharePoint 2013 with their ADFS credentials through the ADFS sign-in site.
Taught the STS about the attributes
Added the mappings to the token issuer
PowerShell pieces for 2 and 3:
$sts = Get-SPTrustedIdentityTokenIssuer $sts.ClaimTypes.Add("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname") $sts.ClaimTypes.Add("http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname") $sts.Update() $map1 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname" -IncomingClaimTypeDisplayName "Given Name" -SameAsIncoming $map2 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname" -IncomingClaimTypeDisplayName "Surname" -SameAsIncoming Add-SPClaimTypeMapping -TrustedIdentityTokenIssuer $sp -AssignmentCollection $map1 Add-SPClaimTypeMapping -TrustedIdentityTokenIssuer $sp -AssignmentCollection $map2
When I try to access the profile manager in script, I get
context = new SP.ClientContext.get_current(); peopleManager = new SP.UserProfiles.PeopleManager(context); userProfileProperties = peopleManager.getMyProperties(); context.load(userProfileProperties); context.executeQueryAsync(onGetUserNameSuccess, onGetUserNameFail);
So my question has two parts:
I think I have to do something in the profile service to make the new properties available, but I'm not clear what
Once the properties are in SharePoint, how do I get them out properly in script?
EDIT: at the moment, the user's e-mail address is the only identifier visible in SharePoint (e. g. in the upper right). We don't have access to the remote AD so we can't do a profile import to pick up other properties through that route.