16

This will be natively supported in Sitecore 9.0, according to the public roadmaps. For now a solution might be to use this module: https://github.com/BasLijten/SitecoreFederatedLogin See my blog on how to achieve this with Sitecore 9.0: https://blog.baslijten.com/enable-federated-authentication-and-configure-auth0-as-an-identity-provider-in-sitecore-9-0/ I ...


11

It might. There is a company claiming to have an option for it, but there is no direct download link and no way to easily verify the claim. https://www.ssoeasy.com/sitecore-sso/ That said; you might be better off, going through something like Gigya. Not only will you get SAML, but Gigya opens up for a host of other authentication modes and options. And ...


8

1) Sitecore 9+ natively supports SAML through Federated Authentication. You have to configure it and write your own provider. These links will guide you through this process for Sitecore 9: Usage in Sitecore - https://doc.sitecore.net/sitecore_experience_platform/developing/developing_with_sitecore/federated_authentication/...


8

Disclosure: answer taken from Securing the password recovery experience in Sitecore 8 by Anders Laub Christofferson First we do some configuration re-organizing. We copy paste the old passwordRecovery pipeline and call the new one confirmedPasswordRecovery <?xml version="1.0" encoding="utf-8" ?> <configuration xmlns:patch="http://www.sitecore.net/...


7

They are all slightly different things and do not necessarily need to be in sync: <forms name=".ASPXAUTH" cookieless="UseCookies" timeout="20" /> Is a Forms Timeout and is the length in time that the auth cookie is valid. Once this time is reached, the cookie will no longer be valid and the user will no longer be authenticated. <sessionState ...


6

I cannot give you a detailed answer but you should know that in the future (not yet scheduled) the AD module will be retired and Sitecore will move away from the Microsoft Membership model and towards Microsoft Identity. This introduces support for the Microsoft.Owin authentication middleware. This can be used as a replacement for the AD module. Owin ...


6

Yes, you can use virtual users in XM: Sitecore also supports Virtual Users, which is a transient user account system that you can use, for example, when integrating with custom authentication systems where an ASP.NET membership provider is not available or possible. A Virtual User is a user that Sitecore does not retrieve or store through an ASP.NET ...


5

I am afraid this question is quite extensive. Sitecore uses ASP.NET membership, role and profile providers. As a starting place, please check this Security API Cookbook. This will give you a really good overview of concepts and also sample code related to Sitecore User Management, authentication, authorization and user profile management. I am sure ...


5

You can use SSO software to treat all of the sites as part of a single 'authentication' realm. That way you log in once and then each site pings back to your SSO software to get the token or authentication confirmation. Shibboleth One example of SSO Software is Shibboleth. It acts as a central gatekeeper and you can set up Service Providers on your server to ...


4

This sounds like you want visitors to be able to login to your site. Unless they have accounts in the Sitecore database already, you probably need to integrate using SSO or by using a user store such as Active Directory. Sitecore has an Active Directory integration which you can download here: https://dev.sitecore.net/Downloads/Active_Directory/1_3/...


4

Probably might help someone. I managed to figure this out as the issue was on the Controller Action for SignOut. Sitecore handles the Owin Middleware integration little differently from Asp.NET. Below is the code for my Signout Action. Here please note, we need to pass the IDP Name "AzureADB2C" explicitly for Sitecore to know which provider is being logged ...


3

No. Not for Extranet users. If a Sitecore license restricts the number of concurrent users, that restriction applies only to CMS users, not to visitors to or extranet users on the published sites. Source: Visitors and Users in the Sitecore ASP.NET CMS


3

I found that there is a configuration setting that can be enabled which runs the preview mode with the currently logged in user (an authenticated user) instead of the default/anonymous user. It's called Preview.AsAnonymous, and setting this setting to false will allow users to preview as the currently authenticated user instead. Source: USING AN ...


3

Separate Site Strategy Given your clarifications, have you considered creating a separate site on which to host this protected content? In the site definition you can specify the security domain, and therefore limit it to Sitecore users/authors. Quick Fix Consider: extranet\anonymous is different from sitecore\anonymous Sitecore's user names are actually ...


3

I have an old support ticket with a confirmed bug by Sitecore Support (on Sitecore 6.5 and 8.0) that a homepage with broken inheritance can lead to a no-layout error. We did get a patch for it (number 325160). If applicable, you should be able to get it from Sitecore Support as well. I did find the issue as fixed in the release notes of Sitecore Experience ...


3

You can use a virtual user to accomplish this. This blog from briancaos explains you exactly how. A virtual User is (as the word says) a memory-only Sitecore user that is created "on the fly". Once you have authorized your user (custom code for your login system), you can create a virtual user that Sitecore will recognize as a normal user. var user = ...


3

Not sure this is what your looking for, but if you add: requireLogin="true" To your site definition, Sitecore will not allow unauthorized users to view the site. I'm not sure how it will behave without a loginpage.


3

I've figured out the answer based on the comment from @Gobinath and answer of this thread. So, first you must add NEW config for these Owin and IdentityServer stuffs and don't touch your previous version of these processes (before IdentityServer, in my case it's working properly without IS) <configuration> <sitecore> <pipelines> <owin....


3

If you issued a redirect with second parameter being default, true, this explains it. What happens in default is, the redirect gets called and then throws an exception to stop further processing. Which, in your case, means that after your processor runs - you abort the pipeline and Sitecore's OWin processing steps are never run. See: Why Response.Redirect ...


3

For this, you need to configure loginPage but set requireLogin to false. Your next step will be to remove the access for Everyone on your /sitecore/content/site node and Remove Inheritance. You then need to create a new role, "Authenticated Users" which will get the access from this level down instead. Finally you need to re-allow Everyone into the few ...


3

This is the support help I got and fixed it: Could you please try overriding the CheckDomainGuard processor using the following: namespace CustomNamespace { public class CustomCheckDomainGuard : Sitecore.Owin.Authentication.Pipelines.CookieAuthentication.SignedIn.CheckDomainGuard { public CustomCheckDomainGuard(BaseLog log) : base(log) ...


2

I've seen this error when logged in to the Sitecore backoffice and then attempting to log into the site as a front-end member in the same browser. I don't believe Sitecore can handle this situation gracefully by default and logs this error. Haven't looked at the core code but likely this is likely due to multiple identities on the same auth ticket and ...


2

If login fails, you could try to fetch the user and check the Membership user object properties for the status. You can detect the IsApproved flag this way, but not verify the password. But you actually do not want to give that kind of information. Just tell the user that his account is blocked, don't tell him that the password was correct. As he can't ...


2

First, have a look at this post that will help you to get started with learning Sitecore. Once you have a handle on Sitecore, you are going to have to decide what kind of membership provider you are going to use. I cannot make a valid recommendation on this, as the decision will ultimately be based on your requirements, but I do recommend that you at least ...


2

As mentioned already, a Virtual user is transitory - it cannot be persisted from visit to visit. So you need to look at this differently. When integrating with an external authentication service, such as ADFS or Azure AD - the login persistence occurs with the authentication service, not in Sitecore. So when the user goes to a secured page in Sitecore - ...


2

Try to pass the persistent paramenter: Sitecore.Security.Authentication.AuthenticationManager.Login("extranet\\" + username, password, persistent: true, allowLoginToShell: false);


2

I got the same issue, with Sitecore 9 as a PAAS on Azure. There seems to be some conflict between webforms authentication/authorization in Sitecore and what Azure uses. I did'nt find a direct solution, but as a work around i used an HTTP auth module to intercept and challenge using "Basic" or "Digest" authentication/authorization. Link Here Now this comes ...


2

Virtual user information is saved in Session. By default Sitecore configuration doesn't share sessions information between few CD servers. That is why one CD server doesn't know anything about logged in users on others CD servers. You have few options, how to solve it: Configure your hosting environment to use sticky load balancer. Link that was mentioned ...


2

You need to pass the token (received in the first request) in the header like: xhr2.setRequestHeader('token', val);


2

I know this is kinda old now, and just to supplement @GeorgeTucker's response, here is a maintenance script I have been using for this cleanup. Basically these tickets control the "Remember Me" feature of the authentication module. select [key] 'k', SUBSTRING( [value], CHARINDEX( '^', [value], CHARINDEX( '^', [value] ) + 1 ) + 1, 16 ) 'ExpiryDate' into ##...


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