EPiServer security on standalone dev machine

November Happy Hour will be moved to Thursday December 5th.

AI OnAI Off

Home / Forums / Legacy forums / Installation and security /

EPiServer security on standalone dev machine

Dany Wu

Vote:

Hi folks,

Here is my security settings in web.config:

</providers>

</roleManager>

</providers>

</membership>

<roleManager enabled="true" defaultProvider="WindowsRoleProvider" cacheRolesInCookie="true">
      <providers>
        <clear />
        <add name="MultiplexingRoleProvider" type="EPiServer.Security.MultiplexingRoleProvider, EPiServer" provider1="SqlServerRoleProvider" provider2="WindowsRoleProvider" providerMap1="SqlServermembershipProvider" providerMap2="WindowsMembershipProvider" />
        <add name="WindowsRoleProvider" applicationName="EPiServerSample" type="EPiServer.Security.WindowsRoleProvider, EPiServer" />
        <add name="SqlServerRoleProvider" connectionStringName="EPiServerDB" applicationName="EPiServerSample" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
      </providers>
    </roleManager>
    <membership defaultProvider="WindowsMembershipProvider" userIsOnlineTimeWindow="10">
      <providers>
        <clear />
        <add name="MultiplexingMembershipProvider" type="EPiServer.Security.MultiplexingMembershipProvider, EPiServer" provider1="SqlServerMembershipProvider" provider2="WindowsMembershipProvider" />
        <add name="WindowsMembershipProvider" type="EPiServer.Security.WindowsMembershipProvider, EPiServer" deletePrefix="BUILTIN\" searchByEmail="true" />
        <add name="SqlServerMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="EPiServerDB" requiresQuestionAndAnswer="false" applicationName="EPiServerSample" requiresUniqueEmail="true" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" passwordStrengthRegularExpression="" />
      </providers>
    </membership>

I usually work while connected to the network on our AD domain. This is my first time working on a standalone laptop and I cannot log on to the admin/edit backend. I'm not entirely sure if this is because I am not connected to our AD, or something else. Is there any way I can bypass this? My ASP.NET security knowledge is not quite up there - any suggestions would be greatly appreciated.

Thanks,
Dany.

#49165

Mar 07, 2011 23:28

bergdaniel

Vote:

If you just need to bypass the edit/admin URL path then you can uncomment the <authorization>...</authorization> element for the edit and admin path. Do note that while this would grant you access to these areas some functionality might not be working properly since EPiServer CMS does not see you in any roles (you were just let in without saying hello to Mr. Security... :)). Another option would be to add yourself to the "Administrators" group locally. This should grant you access with default settings.

 <!--<authorization>
        <allow roles="WebAdmins, Administrators" />
        <deny users="*" />
      </authorization>-->

#49172

Mar 08, 2011 8:38

bergdaniel

Vote:

I wrote two posts a while back on security with EPiServer CMS, maybe they can help:

http://blog.bergdaniel.se/post/Setting-up-user-permissions-in-EPiServer-CMS-part-1.aspx

#49173

Mar 08, 2011 8:40

Dany Wu

Vote:

Thanks - you're right though, some things didn't work. In the end I ended up using the mixed role and membership providers. While I was connected to the domain I quickly created a user in the SQL provider :o)

#49179

Mar 08, 2011 10:42

bergdaniel

Vote:

Alright, glad it worked out! :)

#49181

Mar 08, 2011 10:55

This thread is locked and should be used for reference only.