Hot answers tagged claims
3
Answering myself...
I changed the script to perform these operations :
Create the webapp with only Windows Auth
Enable Claims authentication on the web app
Add the remaining auth providers
Extend the web app (passing all providers is working)
Here the updated script :
Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction 0
$winAp = ...
2
You can get claims through below code:
var claimsPrincipal = Page.User as IClaimsPrincipal;
if (claimsPrincipal != null)
{
IClaimsIdentity claimsIdentity = (IClaimsIdentity)claimsPrincipal.Identity;
var userClaims = claimsIdentity.Claims;
}
But if you want to add the claim at the time of ...
2
The claims included in your token are only used to make authorization decisions inside of SharePoint. The custom claims provider provides claims augmentation (adding claims to your token) and claims lookup (people picker functionality).
If you want to have user properties in the user profile service application, you still have to configure an import ...
1
Authentication is managed at the web application level only. It is not possible to have sites within the same web application use different authentication providers unless the entire application supports those providers.
Maybe this article will help: http://msdn.microsoft.com/en-us/library/hh237665.aspx
1
You state in the picture that the site collection at '/' doesn't even exitst.
It should otherwise you're running unsupported unless every site collection is a host header site collection in the web application. See SharePoint 2010: Supportability of unprovisioned root site in a SharePoint web application
1
We finally found a solution, that consisted in changing the client library.
We especially use the component described here : Support for NTLMv2 with Apache HttpClient using JCIFS.
A sample code we used:
QueryServiceStub queryServiceStub = new QueryServiceStub("SHARE_POINT_ASMX_URL");
List authPrefs = new ArrayList(1);
authPrefs.add(AuthPolicy.NTLM);
...
1
I'm quiet mystified by how it works with UserY, it should always fail.
When running with Claims without NTLM the only way to pass credentials is through a FedAuth cookie with your SharePoint STS SAML token. To get that token you have to call the SharePoint STS with a SAML token from your identityprovider (ADFS?). To get that token you have to call the ...
1
Someone actually built a web part extracting all claims from authenticated session
http://allthingssharepoint.wordpress.com/2011/04/14/sharepoint-claims-web-part/
C:\Marius
1
IClaimsIdentity currentIdentity = System.Threading.Thread.CurrentPrincipal.Identity as IClaimsIdentity;
//var userName = currentIdentity.Name;
foreach (Claim claim in currentIdentity.Claims)
{
// claim
}
1
everything remains as it is, you have a nice token of your claim that you can manage in your webpart, only that you will be forced to implement a custom provider claims to search for users or groups sull'ldap (people picker) and transform the result into a claim. I hope I explained myself
visit this link:
http://ldapcp.codeplex.com/
Only top voted, non community-wiki answers of a minimum length are eligible
