AspNetSqlMembershipProvider Question
-
Hi guys. I used AspNetSqlMembershipProvider to create the membership system for one of my sites. It isn't working consistently. I'd like to change some of the settings I originally chose in my web.config. I'm worried that if I do this it will screw up the accounts that have already been created. I need advice about the best way to go about this. Currently, I have this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="true" passwordFormat="Hashed" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'd like to change it to this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" applicationName="/" requiresUniqueEmail="true" passwordFormat="Clear" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'm worried that changing from hashed passwords to clear passwords and getting rid of require question and answer now that 100 or so users have already signed up will hose all the previous accounts and make it impossible for them to log in. The reason I'm doing this is that users are complaining about intermittent problems with my CreateAccount, RecoverPassword, and ChangePassword controls, which are set up with default controls. I haven't done anything fancy that should screw them up. I feel like the most exotic part is the portion of the web.config I shared with you. I feel like if I make that less complicated it might solve all my problems. But
-
Hi guys. I used AspNetSqlMembershipProvider to create the membership system for one of my sites. It isn't working consistently. I'd like to change some of the settings I originally chose in my web.config. I'm worried that if I do this it will screw up the accounts that have already been created. I need advice about the best way to go about this. Currently, I have this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="true" passwordFormat="Hashed" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'd like to change it to this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" applicationName="/" requiresUniqueEmail="true" passwordFormat="Clear" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'm worried that changing from hashed passwords to clear passwords and getting rid of require question and answer now that 100 or so users have already signed up will hose all the previous accounts and make it impossible for them to log in. The reason I'm doing this is that users are complaining about intermittent problems with my CreateAccount, RecoverPassword, and ChangePassword controls, which are set up with default controls. I haven't done anything fancy that should screw them up. I feel like the most exotic part is the portion of the web.config I shared with you. I feel like if I make that less complicated it might solve all my problems. But
-
I'm sure there must be a way of doing this through code rather then editing the xml file, trying searching the web for c# code to update membership login
-
Hi guys. I used AspNetSqlMembershipProvider to create the membership system for one of my sites. It isn't working consistently. I'd like to change some of the settings I originally chose in my web.config. I'm worried that if I do this it will screw up the accounts that have already been created. I need advice about the best way to go about this. Currently, I have this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="true" passwordFormat="Hashed" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'd like to change it to this: <membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="15"> <providers> <remove name="AspNetSqlMembershipProvider" /> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="LocalSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" applicationName="/" requiresUniqueEmail="true" passwordFormat="Clear" minRequiredNonalphanumericCharacters="0" maxInvalidPasswordAttempts="4" passwordAttemptWindow="10" /> </providers> </membership> I'm worried that changing from hashed passwords to clear passwords and getting rid of require question and answer now that 100 or so users have already signed up will hose all the previous accounts and make it impossible for them to log in. The reason I'm doing this is that users are complaining about intermittent problems with my CreateAccount, RecoverPassword, and ChangePassword controls, which are set up with default controls. I haven't done anything fancy that should screw them up. I feel like the most exotic part is the portion of the web.config I shared with you. I feel like if I make that less complicated it might solve all my problems. But