Having done this, SharePoint is aware of the Membership and role managers you have created.

Now Let us start creating a web application with claims authentication.

1. Select authentication mode as “Claims Based Authentication”

2. Provide the membership details in Claims Authentication Types section as what you have configured in web.config

3. Select default/custom Sign in page. If you have a custom page, go for that.

4. Click Ok to create the web application.

5. Next thing is to create a Site Collection in the new web application.

6. Select Primary Site Collection Administrator and Secondary Site
Collection. Primary Site Collection Administrator is the domain user and
Secondary Site Collection Admin is from SQL users. SharePoint is able
to resolve both users.

7. Click OK to create top level site collection and site collection is ready to use.

8. Let us log in to the new site collection. SharePoint will provide
you with the default Log in screen instead of automatic log in using
windows authentication. In the default log in screen, there is a control
that talks to Security Taken Service to get authenticated. SharePoint
Site no longer authenticates the users. It is a trust based
authentication mode. Security Token Service trust the users and
SharePoint truest Security Token Services.

Where is Security Token Service?

How Security Token Service understands our providers?

Security Token Service can be found in

We need to configure Security Token Service's web.config with provider details to make it aware of SQL users.

8. 1. Explore Security Token Service application which is a WCF Service and update its web.config file