Tag Info

New answers tagged

0

This is because SharePoint 2010 also creates an auth cookie which is saved to local file. The trick is to force SharePoint 2010 to use a session-based cookie, so that it is destroyed when the page is closed. In order to do that, run the following PowerShell script on the SharePoint WFE: $sts = Get­SPSecurityTokenServiceConfig $sts.UseSessionCookies = $true ...


0

You need to implement a Identity provider on your end and pass saml assertion (some kind of identifier) . Write code to convert to SAML1.1 token because Sharepoint does not understand SAML 2.0.So you need to write a code for this conversion.Then run the powershell scripts so that your web application can trust the claims. ...


1

To configure the Kerberos, you have to perform following steps. Configure SQL Server for kerberos Authentication Create DNS entry for your web application Create SPN for the DNS(you will use to access the SharePoint) Make Changes in Central admin and change authentication To Kerberos. Enable Constrained Delegation here is complete guide and step by step ...


1

If anyone ever has the same problem, I found a solution to this: instead of hardcoding the wreply parameter, I first access the SharePoint site + "/_forms/default.aspx" with a request that does not follow redirects and has the user agent set. The response has a Location header that I get and which contains a wreply parameter. Only the left part (in the Uri ...


1

In my opinion it is not a problem with the AAMs as you can access http://myserver.domain.com/pages/home.aspx and other pages of this site. It sounds to me as if the problem would be located on your root site. Just as a first step: Did you check if masterpage, style sheets, script files etc. are checked in and published? (although I think that at least ...


1

I would recommend JShare. It is Android and Java library for SharePoint. It supports few authentication options including NTLM.


0

Refer the below link which explains how to override the people picker to provide the valid values. http://blogs.msdn.com/b/kaevans/archive/2013/05/26/fixing-people-picker-for-saml-claims-users-using-ldap.aspx


0

Did you try to access http://myserver.domain.com/pages/ Better check claim authentication setting and Claims Authentication Types (NTLM) try to Add the admin user to the site in format (i:0#.w|domain\user).


0

Yes. I'm going to assume that you have a proscribed set of permission that should be assigned to certain users. First work out what your default users should have access to in terms of view/edit/manage etc. for each part of the site. Next either create a new user group or use the Members group. As a general rule you'll likely have a view permission for ...


0

This provides a few good points about drawbacks. If a user is a Windows domain user who has a login and password for Windows, he must still provide another (SQL Server) login and password to connect. Keeping track of multiple names and passwords is difficult for many users. Having to provide SQL Server credentials every time that one connects ...


0

the question has been answered before, look at ashish answer as it implements your code. I think the area your going wrong is in the cookie part. Windows authentication with SharePoint Web Services via SOAP the code is for list authentication but a slight alteration would give you site authentication. The principal is the same!


0

I'm not sure if these articles would apply in your situation but adding an event handler for the ExecutingWebRequest solved the Forbidden errors I was getting when making CSOM calls. Although most of these articles apply to previous versions of SharePoint I was able to get it working with our 2013 environment. ...


0

If you want the navigation to display without regard for security, then you will need to maintain the navigation manually instead of relying on the automatic "Show sites" capabilities. However, I would suggest that links to site for which you do not have permission be hidden. This will reduce the number of times users will get the Access Denied page.


0

You have to implement security. User Profiles are not security. You can do this by granting access to your users by adding them to a group of "Approved Users" in the same way you added them to the OU for synchronization.


0

You might need to you try deactivate the “HTTP Activation” feature of .NET 3.5 and .NET 4.5 and re-enabled one by one (1st .NET 3.5, 2nd .NET 4.5 ) them after deactivation then do the IISReset Re-enable Form Authentication ...


0

Question # 1 Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013.Due to the widespread use of claim-based authentication for user authentication, server-to-server authentication, and app authentication, we recommend claims-based authentication for all web applications and zones of a SharePoint 2013 ...


0

I usually just use the membership provider only for authentication, and store the profile fields directly in SharePoint user's profile.


1

You can use the Profile Provider for this, which let's you associate any arbitrary information you wish with the user. Alternatively, you could create your own table(s) that store additional user-related information. This is a little more work since you're on the hook for creating your own tables and creating the code to get and save data to and from these ...



Top 50 recent answers are included