0

I'm working on a legacy website that uses Forms Authentication and was using Classic Managed Pipeline Mode. The default Membership.ApplicationName is read from web.config and can be changed in code to match the application name to allow users to log in on different portals. This works fine in Classic mode, but in Integrated mode the Membership.ApplicationName is null and can't be changed. If it's set to the application name, the value stays at null. Other values are read fine from the web.config

<membership defaultProvider="Database">
  <providers>        
    <add name="Database" 
         connectionStringName="SkylineMembership" 
         requiresQuestionAndAnswer="false" 
         applicationName="/" 
         type="Eprint.Skyline.Web.Pages.ApplicationProvider" 
         requiresUniqueEmail="false" 
         minRequiredPasswordLength="1" 
         minRequiredNonalphanumericCharacters="0" 
         passwordStrengthRegularExpression="" 
         maxInvalidPasswordAttempts="99" />
  </providers>
</membership>

For example the default value for maxInvalidPasswordAttempts="99" is read OK, but applicationName is always Null, and stays at Null even after being set to another value in code.

The code to set the application name is on a BasePade that is inherited on all the user facing pages. e.g. public partial class Login : BasePage' The website code is using Code Behind, not MVC

Any ideas why I can read and set the Membership.ApplicationName when using Classic mode but not when using Integrated mode? This has got me baffled for a couple of days now.

Paul Clark
  • 43
  • 5
  • 1
    Microsoft only defines an abstract property https://learn.microsoft.com/en-us/dotnet/api/system.web.security.membershipprovider.applicationname?view=netframework-4.8, so it is up to the developers of `Eprint.Skyline.Web.Pages.ApplicationProvider` to decide what's the behavior (under different application pool modes). – Lex Li Apr 09 '21 at 19:44
  • Thanks for the heads-up Lex Li. The "problem" was down to a poorly written implementation of Eprint.Skyline.Web.Pages.ApplicationProvider – Paul Clark Apr 12 '21 at 10:27

1 Answers1

0

The "Problem" was caused by a poor implementation of code in the project (Eprint.Skyline.Web.Pages.ApplicationProvider). Changing the type to "System.Web.Security.SqlMembershipProvider"in web.config fixed the problem

<membership defaultProvider="Database">
  <providers>        
    <clear />        
    <add name="Database" 
         connectionStringName="SkylineMembership" 
         requiresQuestionAndAnswer="false" 
         applicationName="/" 
         type="System.Web.Security.SqlMembershipProvider"
         requiresUniqueEmail="false" 
         minRequiredPasswordLength="1" 
         minRequiredNonalphanumericCharacters="0" 
         passwordStrengthRegularExpression="" 
         maxInvalidPasswordAttempts="99" />
  </providers>
</membership>

Thanks @Lex Li for the heads-up

Paul Clark
  • 43
  • 5