Hi all,

I am writing a custom membership provider (authentication) that authenticates users against another database (sql database) of a CRM application, which in fact utilizes the AspNetMembership provider.
I followed several articles on how to do that and what I found, is suggestions on building a membership provider such as LiveID or OpenID.

The problem with these two providers is that once you authenticate against OpenID or Live ID, DNN requires that you create an account in the DNN database and associate it with the first one.

What I want to do, is to be able to authenticate against my provider, without having the need to create an account in the DNN Database (as LiveID and OpenID do).
The same as with creating or updating an account in my CRM's database.

Is there a way of building a Login control that when authenticating against the CRM, DNN is 'aware' of the logged in user?
Can DNN 'read' the roles in my database and respectively when creating a page, assign view rights to these roles?

Please advise