· All Windows users' favorite team is "Blazers"
· For FBA users:
o user1 through user15 have a favorite team of "Blazers"
o user16 through user30 have a favorite team of "DVK Jovenut"
o user31 through user50 have a favorite team of "Shanghai Tigers"
protected override void FillClaimsForEntity(Uri context, SPClaim entity,
· ClaimProviderAssembly and ClaimProviderType are just using type properties of the custom provider class that we wrote
· ClaimProviderDisplayName uses the internal static property that we created on our claims provider class. That's why we did that - just so we could reuse it in our claims feature receiver
· The FeatureActivated event calls our special internal method for activating properties
How about sharing your code for the web part that displays the claims?
Hi Rick, I posted the code for the part previously at http://blogs.technet.com/speschka/archive/2010/02/13/figuring-out-what-claims-you-have-in-sharepoint-2010.aspx.
what kind of information is available about the identity and the resource being accessed when the FillClaimsForEntity(Uri context, SPClaim entity, List<SPClaim> claims) method is called?
For example, do I get the url and the headers from the httprequest in the SPClaim object that is passed to this method?
I am very new to sharepoint development arena. I am working at a company where we are implementing custom claims provider (as compared to windows previously). I am learning the architecture of SP2010 and ADFS v2 and we have AD like stuff which has all the profile and user, groups information. Could somebody help me out in figuring out what are the stuffs that I need to actually start working/implementing custom claims provider people picker SP 2010.
any thoughts on social.msdn.microsoft.com/.../6a90bbb0-6100-42e4-8163-a5ec17fdf408
Hi Nice article
I have written a custom STS and membership providers for various applicatrions and have now modified it to work with SP 2010 and have them working. However I am new to Sharepoint programming. I understand after reading the articles and have used them to create a custom claims provider that queries a database for the hierarchy etc.
However I have no idea how to create a SP feature for SP2010 can you let me have some info or point me to an article where I can see how his done.
Are my new best friend! If I could only express in words the headache you helped me avoid. Thank you much for sharing.
I am trying to access the existing claims PRIOR to augmenting with custom claims. I can't see to access the users existing claims in the method "FillClaimsForEntity". Any thoughts?
I just ran this example, worked the first time.
Made a change to what claims I wanted to have, deployed, and it's not updating in Sharepoint. I think it's because the feature activation/deactivation is not uninstalling (?) or updating our SPClaimProvider code in the GAC? Anyone else have this problem?
I successfully implemented your example. Then I had to remove Custom Claims Provider I wrote. I done it using Uninstall-SPFeature command. Custom Claims Provider was removed - I can't see it in the people picker form which is OK for me. But I can't see WingtipSTS and their claim types in the people picker. On the left side of the form I can see only following items:
- All Users
- Active Directory
But I should see all items below, because I still use WingtipSTS for my Sharepoint web application:
Is it possible to set up Sharepoint to have previous (standard) functionality in the people picker form?
Thanks for the blog post! Here's a link to the project. code.msdn.microsoft.com/SharePoint-2010-Writing-87dbee1d It would be awesome to have the code bundled as a VS2013 SharePoint 2013 project. That way it's ready to go for debugging and development.
We thought a Custom Claim Provider would be a great way to add claims to Windows authenticated users in Sharepoint 2010. But the custom Claim Provider is not called only at login time, it is called on every request to the server. So the custom claim provider is called on every web and for every picture on that web. Since we have a lot of claims to augment, this will be devastating for the SQL server.
If I add another authentication provider (FBA) for that zone, it starts augment claims only at login time as it should, even if I login as a Windows user.
Is this a known issue and is there a common solution for this? Will it work in Sharepoint 2013?
To anyone using the above example, please see this post:
When it comes to SharePoint 2013 the above is incomplete without this footnote. Before I learned of it, and in spite of the detailed instructions found here, I had no success with deploying a claims provider.