Tag Info

New answers tagged

0

We discovered that it was an issue with the separator used in the compound claims. We were using | (pipe) as the field separator. The claim was something like contoso|user|1234 The suspicion is on the content side, the encoded value for the pipe was stored (as evidenced in examining the claim values in the permissions) but during crawl/gatherer/processing an ...


1

This answer assumes you are using a standard SQL Membership Provider and vanilla database. (And this is not really a SharePoint issue, this is more of a .NET issue you are implementing in a SharePoint context.) Essentially, what you want to do is insert some rows into a database. There are a number of ways to access a database, but I prefer Entity ...


0

The first thing I would do is run the following STSADM.EXE -o Sync -listolddatabases 30 STSADM.EXE -o Sync -deleteolddatabases 30 The second command is only necessary if the first one returns results. If you for some reason the user is still showing up, Even thought the Get-SPUser is not returning the user I would manually check the userinfo list for ...


0

You would have to create your own STS. You could try IdentityServer as a base, but it is not trivial. Another option would be to use something like Auth0 (auth0.com). They support this scenario out of the box.


0

This cannot be possible as there is no access token present in case of High Trust App For low trust apps, there is access token which contains audience and nameid to create and user based authetication


0

It is not possible to have claims and classic authentication at the same time on a web application. If you are using claims-authentication, you can specify multiple authentication providers on one zone; or extend your web app to multiple zones, and use one authentication provider per zone. For instance, Windows-authentication (NTLM) on the Default zone, ...


0

Here is how I eventually solved the problem: using System; using System.ComponentModel; using System.Web; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using Microsoft.SharePoint; using Microsoft.SharePoint.WebControls; using System.Data.SqlClient; using Microsoft.SharePoint.Administration.Claims; using ...



Top 50 recent answers are included