Hot answers tagged

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 = ""; ...


4

The sp_install user should only be used to execute the base/initial installation of SharePoint. The sp_farm account is used after the setup in the SharePoint Configuration Wizard. And after that all Services should run under SP_Farm Account as expected. I don't know if you can separate the accounts in the AutoSPInstaller but i am sure it will be ok to only ...


4

Short answer, no. You don't need it. It's just a super, no bars account that all the rest of the accounts' permissions are designated from. As part of the "best practice" its one of those accounts that Microsoft suggests to set everything up with the least-privileged account security model. AutoSPInstaller is a great tool I still rely on today, but running ...


3

I've always intalled my SP farms with SPInstall (often named SPAdmin in my cases). When prompted by the setup program for the account to run the farm with, I enter SPFarm. After that, everything is usually configured OK, i.e. SP Timer, CA pool, etc. run Under SPFarm. I then use SPInstall (aka SPAdmin) to log on the machine and administrate SP (i.e. access CA ...


3

Their are 3 differnt way to implement the claims authentication. Windows authentication methods NTLM Kerberos Anonymous Basic Digest Forms-based authentication methods LDAP SQL Server database or other database Custom or third-party membership and role providers SAML token-based authentication methods AD FS 2.0 Third-party identity provider LDAP ...


3

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 ...


3

Multiple endpoints in the same relying trust is possible if the SPTrustedIdentityTokenIssuer has UseWReplyParameter enabled. This should help out with SharePoint Hosted and Provider Hosted apps. $tit = Get-SPTrustedIdentityTokenIssuer fs.contoso.com $tit.UseWReplyParameter = $true $tit.Update() Please see the following blog: SharePoint and ADFS with ...


2

Just regenerate the token. Add the App For SharePoint nuget package to your console app. Install-Package AppForSharePointWebToolkit Then write the code to generate the token and context object. Uri siteUri = new Uri(siteUrl); string realm = TokenHelper.GetRealmFromTargetUrl(siteUri); string accessToken = ...


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 have to configure the Seprate end point for each Web application. $ap1 = Get-SPTrustedIdentityTokenIssuer -identity "Adfs name" $uri = new-object System.Uri("url of webapp/") $ap1.ProviderRealms.Add($uri, "urn:sharepoint:MySite") $ap1.Update()


2

The solution described here is for SP 2010 but works perfectly fine against SP2013. Summary: You cannot use SharePointOnlineCredentials class. You need to get the FedAuth cookie by making a request against the ADFS server and then attach it to every CSOM request. Update Here are some sample values for all those parameters: wctx = ...


2

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

You will have to set up an high trust app that uses S2S protocol, because your provider hosted app needs to be accessed only by users who has access to SharePoint, also the app will need permission to access the SharePoint resources. Follow this blog to set up an high trust provider hosted app.


1

Hi you can try integrating your SharePoint site with any other popular external providers such as Facebook,Google, Microsoft Live ID etc and authenticate user's by Federated authentication mechanism. You can refer this blog for more details on it.


1

Do your users access SharePoint via FQDN (e.g. http://sharepoint.company.com)? Then you have to add the URL of the SharePoint to a registry key called AuthForwardServerList to get your clients authenticated automatically. See this MS support article for more details on this behavior. I would recommend you to test this on one client and then roll out the ...


1

Be very careful with this design, as it's pretty tricky to do well. Though first, any site template can be used, as the site template doesn't affect authentication. Authentication. You could either: enable both forms and windows auth on the same web app. When a user went to the site, they would get a dropdown selection that asked them if they wanted to ...


1

User profiles must be created initially from an LDAP (or other approved directory) this does not include SQL. You have to have a domain account to match the Profile to. This can also happen when a user hits a SharePoint site for the first time. Once the Profile is created you can update it in a number of different ways. If you want to use a SQL data source ...


1

So the solution is to run this PowerShell script on the web application providing the information: Add-PSSnapin Microsoft.SharePoint.PowerShell -EA 0 $localFarm = Get-SPFarm $webapp = Get-SPWebApplication "http://XXX---URL_OF_PROVIDING_WEBAPP---XXX" # Remove old web.config modifications of MyAuthenticationProvider $oldMods = @(); ...


1

I had this same issue, and I am not sure what I changed that caused this to happen. After I first installed SharePoint it was working, then after modifying a lot of things, it stopped working. How I fixed this very frustrating issue. First I logged into the SharePoint server and ran the SharePoint 2013 Products Configuration Wizard. Next I went to ...


1

By default, SharePoint Server supports these authentication methods: Anonymous AuthN Basic AuthN NTLM AuthN Digest AuthN Kerberos Protocol Transitioning/Constrained Delegation Windows-Claims Claims MultiAuth Claims Mixed Mode. The CMIS Producer is available by default in SharePoint Server for on-premises deployment Consider you create one app and it ...


1

//Use below commented line if want to connect through some user ID and password Instead of windows authentication //context.Credentials = new NetworkCredential("userId", "password", "domain"); Web rootWeb = context.Site.RootWeb; context.Load(rootWeb); BasePermissions bp = new BasePermissions(); ...


1

To get the list of TIPs, run: Get-SPTrustedIdentityTokenIssuer | Select Name Then you can run: $tip = Get-SPTrustedIdentityTokenIssuer "tipName" If you only have one TIP, you can just run: $tip = Get-SPTrustedIdentityTokenIssuer What LDAPCP accomplishes is that it creates a connect to the on-premises directory (e.g. Active Directory) and resolves ...


1

Very often the SharePoint CentralAdministration does not run on the default Port. As you use SSL, it would be 443. InternetExplorer has some known bugs regarding Kerberos. One of it is the use of non-standard ports. A lot of details to all known Kerberos issues can be found here: https://technet.microsoft.com/en-us/library/gg502606%28v=office.14%29.aspx. ...


1

looks like duplicate entries for connectto, So Please removes duplicate entry using the following PowerShell $uri2 = new-object System.Uri("https:// connectto.sp2013dev.com") $ap = ProviderRealms.Remove($uri2) I would highly recommend that create the separate relying party package for each web application and then configure it in SharePoint.



Only top voted, non community-wiki answers of a minimum length are eligible