Hot answers tagged sso
Please follow these steps: 1- Open Microsoft Internet Explorer. 2- Select Tools > Internet Options. 3- Click the Advanced tab. 4- Under the Security group select Enable Integrated Windows Authentication and click Apply. 5- Click the Security tab. 6- Select the Local Intranet icon and then click Sites. 7- In the Local Intranet dialog box, click ...
A quick Bing search shows a few options. http://sharepoint-live-authentication.shetabtech.com/ - Paid option http://openidmembership.codeplex.com/ - free option http://blogs.perficient.com/microsoft/2011/01/updated-adding-an-openid-claims-provider-for-ad-fs-2-0-to-extend-access-to-sharepoint-2010/ - a how-to
In its simplest form, claims are simply statements (for example, name, identity, group), made about users, that are used primarily for authorizing access to claims-based applications located anywhere on the Internet. Each statement corresponds to a value that is stored in the claim. It is depend, A claim type provides context for the claim value. It is ...
SharePoint does not perform authentication. What you are trying to do is not possible. The page you reference is for configuring SharePoint web applications. Microsoft's single sign-on approach is based on ADFS2.0. I recommend you deploy ADFS and configure SharePoint and your other application to both delegate authentication to it.
Single Sign-On means something else to different people - e.g. one-time authentication and authorization across multiple systems (front or back-end) or simply being able to delegate credentials from the system you are logged-on to other systems while accessing a services or data. In SharePoint 2010 for Authentication you could either configure Kerberos ...
Yes, it s possible. Set your web application to anonymous access and everything that goes with it. In your sub site, break inheritance, then set up permissions accordingly using groups that are AD only. Someone trying to access the sub-site will be prompted for credentials.
Assuming you have SharePoint on-premise and not 365. Making a client-side only solution is easy if you use apps (SharePoint hosted), but you would have to deploy the app to SharePoint to be able to do cross-domain request. Microsoft introduced two main solutions for querying cross-domain, SP.RequestExecutor.js for JSOM and /_api/SP.AppContextSite for REST, ...
Unfortunately due to the 'home-realm discovery' set of challenges, there's no way Office 365 can know where your users come from in order to be able to transparently redirect them to your ADFS server for their logon token. This is because they cannot guarantee that the intention is to specifically logon with only the organisational account bound to the ...
I was able to get this to work using the approach above outlined in my question - i was able to copy Microsoft.Sharepoint assembly from server and reference it in my ASP.NET project. The Microsoft.SharePoint.Administration.Claims namespace is found in the Microsoft.Sharepoint assembly
The key is to have both SharePoint and your app use the same authentication source. So, either your app must change to Windows Auth (aka Integrated NTLM), or SharePoint must use forms (or claims that is based on the same user store).
Only top voted, non community-wiki answers of a minimum length are eligible