Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The idea you should follow in the case of custom membership/role providers is similar to what <a href="http://sdn5.sitecore.net/Products/AD.aspx" rel="noreferrer">AD module</a> lists in <a href="http://sdn5.sitecore.net/Products/AD/Documentation.aspx" rel="noreferrer">its setup instructions</a>. The entire process can be split into several steps:</p> <ul> <li>Adding a connection string to connectionstrings.config</li> <li>Adding membership/role provider definitions to the system.web section of web.config</li> <li>Activating switchers</li> <li>Creating a new domain for the users/roles from custom provider</li> <li>Adding domain/provider mappings</li> </ul> <h2>Adding a connection string</h2> <p>This is pretty straightforward and it seems this is what you've done already. The point is to have a connection string to the database you can then reference from the custom providers.</p> <h2>Adding membership/role provider definitions</h2> <p>Another simple step - just add a membership provider definition (<code>myProvider</code> in your case) under <code>system.web/membership/providers</code> section in web.config, and add a role provider definition under <code>system.web/roleManager/providers</code> section. The order is not important. At this point, you do not modify any other provider definitions in the mentioned sections.</p> <h2>Activating switchers</h2> <p>This is where it becomes complicated. First off, DON'T CHANGE the <code>@defaultProvider</code> attribute value. It is <code>'sitecore'</code> by default and it should stay as is. Instead, find the provider called <code>"sitecore"</code>, and change its <code>@realProviderName</code> attribute value from <code>'sql'</code> to <code>'switcher'</code>.</p> <p>The provider named "switcher" is responsible for all the magic behind switching the providers and combining the results of GetAll/Find methods.</p> <h2>Create a new domain</h2> <p>You should create a new domain for the users/role you'll take from your custom DB through your custom providers. Something like this:</p> <pre><code> &lt;domain name="myDomain" ensureAnonymousUser="false"/&gt; </code></pre> <p>The <code>@ensureAnonymousUser</code> attribute being set to false means that Sitecore won't add an anonymous user to your domain, so there won't be <code>myDomain\Anonymous</code>. This is usually the desired behavior for the custom domains.</p> <h2>Adding domain/provider mappings</h2> <p>This is the last step to let Sitecore know which domain is served with each provider. One provider can handle multiple domains (default Sitecore SQL provider stores the users from 'sitecore' and 'extranet' domains), but not vice versa.</p> <p>So, open the main web.config file and browse to the <code>configuration/sitecore/switchingProviders</code> section. Add something like this for memberhip subsection:</p> <pre><code>&lt;provider providerName="myProvider" storeFullNames="false" wildcard="%" domains="myDomain" /&gt; </code></pre> <p>and the similar thing for roleManager subsection:</p> <pre><code>&lt;provider providerName="myProvider" storeFullNames="false" wildcard="%" domains="myDomain" /&gt; </code></pre> <p>After this, the users from your DB will be visible as <code>'myDomain\user'</code> in UserManager, the same is true for roles. The <code>@storeFullNames='false'</code> means that your DB stores the users/roles without domain prefixes, just the local names. Wildcard should be the default value in case your custom source is SQL (which obviously is).</p> <p>That's it, and now it should work! :-) The details of the steps above are described in <a href="http://sdn5.sitecore.net/Articles/Security/Low_level_Sitecore_Security_and_Custom_Providers.aspx" rel="noreferrer">this article</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POSitecore authenticate users against external membership database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USYan Sklyarenko
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSitecore authenticate users against external membership database
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you so much! This is just what I needed.
      singulars
      1. PO
      1. USMatthew Dresser
    2. COHi Yan, I'm getting the error `'A domain specified in the Sitecore.Security.SwitchingMembershipProvider provider/domain map could not be found. Domain name: myDomain'`. I created the domain under `configuration/sitecore/domainManager/domains` is this the correct place to add the domain?
      singulars
      1. PO
      1. USMatthew Dresser
    3. COTry to add it to the /App_Config/Security/domains.config file
      singulars
      1. PO
      1. USYan Sklyarenko
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload