New answers tagged

0

The SharePoint People Picker will only show users from the user sources that are enabled for the current web application's zone. So if you enabled FBA but removed unchecked Windows Authentication (for instance to only allow FBA users to sign on this zone), then they won't be able to pick AD users. If you want to see both FBA and AD users, you must enable ...


2

When using 'Embed Code' it creates a Script editor webpart/control which itself resides in the asp.net <form>, so this won't work as you can't have a form in a form. The issue is that the javascript can't select your own form (not by getElementById, not by jQuery) so the submit()-function simply doesn't exist. What you can try is to embed the working ...


2

You most only have a single profile for any one individual. SharePoint sees the identity as two different users, and they cannot be 'merged' together. If you are unable to switch to a single provider for all Web Applications/users, you may want to look at one UPA Service Application per Web Application. To give you an example, you may have a user come ...


6

Your code needs two changes to work with both SharePoint On-Prem and SharePoint Online. First, change the type of the second parameter from NetworkCredential to ICredentials. Second, you need to add a header value to the request. private static string GetFormDigestValue(string siteurl, ICredentials credentials) { string newFormDigest = ""; ...


0

I doubt this is a double-hop issue since you're passing explicit credentials. However, I don't understand this piece of code: NetworkCredential nc = new NetworkCredential(USER, PWD, DOMAIN); CredentialCache cc = new CredentialCache(); cc.Add(uri, "NTLM", nc); ctx.Credentials = cc; Should simply be IMO: ...


1

I was able to find a solution for this by decompiling the CSOM and watching the exchange via Fiddler. *If someone with 300+ reputation can add a "vNext" tag that would be appreciated. It's really hard to find vNext-specific documentation as-is. Yes, you do have to disable MFA. There is no programmatic way around this for now. Microsoft is planning to (or ...


-1

In SharePoint to make cross domain calls, you need to create request using SP.RequestExceutor.JS see the below MSDN links SP.RequestExecutor Access Data from Cross Domain


0

In Windows Authentication (NTLM), getting two 401 before one 200 is completely expected: this is the way challenge/response work. You usually don't notice it with same-domain calls since you're already authenticated with a session cookie.


0

I've always found a quick glance into the Authentication settings in IIS gives a clue to whether basic authentication is being used or not...


0

You have a couple of options: If your users log into their machines with domain credentials, you can add *.intranet.com to the Local Intranet Zone in IE. This will work for IE and Chrome, but not Firefox. You can implement a Single Sign On service. ADFS 3.0 provides this functionality, and can be used in conjunction with Web Application Proxy. With ADFS ...



Top 50 recent answers are included