WCF Membership Provider vs. Special Services Authorization Manager w. user name validator

I am completely new to WCF and I am trying to configure services and got two different tips:

The difference I see is in method two, user credentials are checked every time the services are called, and I don’t need to save the session state on the server, which I like.

I do not understand the concept, and the two solve different problems?

Can someone please help me sort these two out and when to use them?

+3
source share
2 answers

ASP.NET built-in membership providers and roles provide you with ready-made tables and stored procedures in your SQL Server database (and admin GUI) for processing users, defining roles, assigning users to roles, etc.

WCF - , ..

-, - .

, , , , , ASP.NET. - WCF, , , .

. WCF , , (Active Directory, ASP.NET, ).

ASP.NET, - , !

+6

, . - , .

TransportWithMessageCredential - , , , SSL .

- , . .

 <serviceBehaviors>
       <behavior name="myCustomBehavior">
          <serviceCredentials>
             <userNameAuthentication userNamePasswordValidationMode="MembershipProvider"
                 membershipProviderName="MembershipProvider" />
          </serviceCredentials>
       </behavior>
    </servicebehaviors>

 <system.web>
  <membership defaultProvider="MembershipProvider" userIsOnlineTimeWindow="15">
   <providers>
    <clear />
     <add name="MembershipProvider" type="MyApp.AP.SimpleSqlMembershipProvider, MyApp.AP" connectionStringName="APServer" applicationName="/MyApp" />
   </providers>
  </membership>
 </system.web>

, , ,

<userNameAuthentication
   userNamePasswordValidationMode="Custom"
   customUserNamePasswordValidatorType=
   "MyApp.SL.CustomUserNameValidator, MyApp.SL"/>

Username/Password ( ) Username/Password . ,

+3

Source: https://habr.com/ru/post/1728887/


All Articles