Tag Info

New answers tagged

1

Your second guess is right, you have to write some logic to combine the two: merge both claims into a new claim, and give rights to this new claim. When you say "claims based authentication", which provider are you using? Windows or trusted IDP (typically ADFS)? If you're using ADFS, you could use the claims rule language in ADFS to add more claims to the ...


0

I would download the search query tool from https://sp2013searchtool.codeplex.com/ Then do a search for * and look in the primary results tab what the path property contains. Additionally please assert in the search application search schema if the path managed property is queryable (I changed only added refineable):


1

Well AFAIK (and as opposed to what Nikhil says), it is not possible to "merge" your FBA and STS users. For instance, the meaning of your FBA claim (i:0#.f|fba|user1) is this: The part before the first | is created by Sharepoint; you can't modify it. It depends on the provider type, the identity claim, and other stuff. Details about this encoding may be ...


0

In the Custom STS , while adding the to SharePoint group edit the code to add user with (i:0#.f|fba|user1) . Since Sharepoint knows both your authentication providers , it should accept it .


1

About the mapping of "http://schemas.xmlsoap.org/.../name": The New-SPTrustedIdentityTokenIssuer cmdlet has a parameter "-IdentityClaim". The claim type you specify as an identity claim is "encoded" by Sharepoint into the "http://schemas.xmlsoap.org/.../name" claim. I don't think you must configure anything special here, just specify a claim sent by your ...


-1

You are doing it wrong. Always use one single account to query data from other systems. Give one account permission to all mail addresses, then check if the user you are going to query has any permissions or inbox on the exchange server. Maybe create a web services to be hosted on exchange server then use that to be accessed by only 1 account. If its on ...


2

Just confirming, are you using Kerberos? Source: http://msdn.microsoft.com/en-us/library/hh231678.aspx Any service that relies on the Claims to Windows token service (C2WTS) must use Kerberos constrained delegation to allow C2WTS to use Kerberos protocol transition to translate claims into Windows credentials. Did you set up the SPNs correctly? They ...


2

I've also been trying to run this to ground with similar results. My code is very similar to what you have above so maybe I am missing something as well, but what I have found out, is that the Claims to Windows Token Service (C2WTS) creates a windows token that is valid ONLY for that SharePoint box when using web services. You might want to verify that ...



Top 50 recent answers are included