Configure Claims-Based Authentication

v8.3 and later


To authenticate users in Sequence using using claims-based authentication, you need to modify the web.config file for each Sequence site (Windows Services are not required).


  • You must configure all Sequence sites under HTTPS. For more information, see Configure HTTPS for Sequence Sites.
  • Verify that your security token service (STS) supports SAML 2.0, and has a WS-Federation Endpoint.


  1. In IIS, configure the root level authentication for each Sequence site.        
    Anonymous AuthenticationEnabled
    ASP.NET ImpersonationEnabled
    Windows AuthenticationDisabled
  2. In IIS, for the Default Document, add the Default.aspx file for each Sequence site.
    The Default.aspx file must be the only document.
  3. Add the <system.identityModel> and <> sections to the <configSections> section.
    <section name="system.identityModel" type="System.IdentityModel.Configuration.SystemIdentityModelSection, System.IdentityModel, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> 
    <section name="" type="System.IdentityModel.Services.Configuration.SystemIdentityModelServicesSection, System.IdentityModel.Services, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
  4. Modify the <authentication> section under the <sequence.engine> section, to match the following example.        
    1. For claimType, use one of the claim types provided by your STS, which you can match with one of the following Sequence employees table.
      1. Domain/User Name
      2. User Name
      3. Email
    2. For authenticationType, use one of the following (depending on your selection from step 5a.       

    3. <authentication impersonate="false">
          <add type="PNMsoft.Sequence.Security.ClaimsIdentityAuthenticationProvider, PNMsoft.Sequence.IdentityModel.v8, Version=, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" />
          <add type="PNMsoft.Sequence.Security.WSFederationAuthenticationPolicy, PNMsoft.Sequence.IdentityModel.v8, Version=, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" />
        <claims enabled="true">
            <add claimType="" 
      originalIssuer="" authenticationType="" />
  5. Make sure that you configure the modules for the <system.identityModel> section under <system.webServer><modules>. Add the following section to the web.config file.
    <add name="SessionAuthenticationModule" type="System.IdentityModel.Services.SessionAuthenticationModule, System.IdentityModel.Services, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" />
    <add name="WSFederationAuthenticationModule" type="System.IdentityModel.Services.WSFederationAuthenticationModule, System.IdentityModel.Services, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" />
  6. Add the following under the main  <configuration> node.
    <location path="Authentication/Federation">
                           <add verb="GET, POST" path="SignIn.axd" type="PNMsoft.Sequence.IdentityModel.Web.FederationSignInHttpHandler, PNMsoft.Sequence.IdentityModel, Version=, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" />		
                           <add name="Authentication" verb="GET, POST" path="Authenticate.axd" type="PNMsoft.Sequence.Web.WSFederationAuthenticationHttpHandler, PNMsoft.Sequence.IdentityModel.v8, Version=, Culture=neutral, PublicKeyToken=0a1a1b90c1c5dca1" />		
    <location path="FederationMetadata">		
                           <allow users="*" />		
  7. Add the following under the <configuration></configuration> section.      
    • For <audienceUris><add value=> use the URL of the Sequence site you are configuring.
    • For <trustedIssuers><add...> use the following information.      
      • <thumbprint> is the thumbprint of your STS token signing certificate. Make sure there are no spaces, there are no coding errors, and that it is plain text.
      • <name> is the value you used for <OriginalIssuer> in step step 5b.
    • For <federationConfiguration><wsFederation>, use the following information.      
      • <issuer> is the sign-in URL of your STS (where users are directed to log in).
      • <realm> and <reply> is the URL of the Sequence site you are configuring.
  8. <system.identityModel>
    	        	<add value="XXXXX" />
    		<issuerNameRegistry type="System.IdentityModel.Tokens.ConfigurationBasedIssuerNameRegistry, System.IdentityModel, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089">
    		               <add thumbprint="XXXXX" name=" XXXXX " />
    		<certificateValidation certificateValidationMode="None" />
    		<cookieHandler requireSsl="true" />
    		<wsFederation passiveRedirectEnabled="true" issuer="XXXXX" realm="XXXXX" reply=" XXXXX " requireHttps="true" />
  9. Under the <system.web> section, replace each of the following sections wherever they exist.
    <authentication mode="None"/>
    <identity impersonate="true" />
             <deny users="?" />