Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Getting StartedGetting Startedcustom MemberShip login not workingcustom MemberShip login not working
Previous
 
Next
New Post
11/20/2012 2:29 AM
 

i created another custom ASP.NET MembershipProvider, using diff db and Membershp db for login

code-wise everything tested ok, but the Page.User is always null.

What I have, custom db, and another/existing Membership db.

created custom MyProvider,

public class MyMembershipProvider : SqlMembershipProvider{

public override bool ValidateUser(string username, string password) { ...

 void After-ValidateUser-Executed() {

FormsAuthentication.SetAuthCookie(uid, false);

 tested everything worked as expected.

But Page.User is always null, even on next postback (after my custom login)

 

can I make my custom membership login worked in dnn (so Page.User will not be null) ?

 
New Post
11/20/2012 4:32 AM
 
I use HttpModule tracing through AuthenticateRequest and PostAuthenticateRequest, i captured below traces:

AuthenticateRequest ...
sender ASP.global_asax
User
... AuthenticateRequest

PostAuthenticateRequest ...
sender ASP.global_asax
User System.Web.Security.RolePrincipal
Identity AuthenticationType , IsAuthenticated False , Name
... PostAuthenticateRequest

AuthenticateRequest ...
sender ASP.global_asax
User System.Security.Principal.GenericPrincipal
Identity AuthenticationType Forms , IsAuthenticated True , Name ab88rmb9995 // this is what I expected
... AuthenticateRequest

AuthenticateRequest ...
sender ASP.global_asax
User // it's gone!
... AuthenticateRequest

PostAuthenticateRequest ...
sender ASP.global_asax
User System.Web.Security.RolePrincipal
Identity AuthenticationType , IsAuthenticated False , Name
... PostAuthenticateRequest

Is it somewhere the Global/DNN logic overwrite it?

then how I can get my custom login work, without having to create/populate the user into the dnn db? or it's a must?
 
New Post
11/21/2012 6:46 AM
 
I use custom login approach, bunch of custom logic, if user not exist/found in dnn, but exist in my custom db, will then migrate the user account (programmatically create the user).

then login will work, as it is using dnn db

not exactly what I planned, as I want to avoid populate dnn db users from my custom db, but at least can get the login work.
 
New Post
4/13/2013 3:32 AM
 

Hi Kelmen, 

I want to create  custom asp.net membership in dotnetnuke, How will do it, Please explain me.


 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting Startedcustom MemberShip login not workingcustom MemberShip login not working


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out