After a brief search in the forum I concluded that my issues has not been raised, how strange it may seem.
So I am creating a new one for this.
My issue is as follows. I have an existing webapplication that uses forms authentication and asp.net membership provider, and installed the Umbraco to use as cms for a subsection of the application.
However, the install overrides my previous configuration for login (changing the login form i.e) and replaces my configured membership and role provider to use its own.
Now, the umbraco database is separate from my application database, and thats how I want it. Umbraco editors in its own database and my existing users in my existing database.
Since Umbraco changes my authentication configuration, my application does not work anymore, since all authentication is dispatched to its own login form, and seemingly to its own membership database.
So my question is, and its decisive for my evaluation, if Umbraco requires that all users are in the same membership database.
If so, what is the best solution: moving my existing user to the umbraco database(I rather not), or create the roles that umbraco needs i my existing database and use my old membershipprovider?
umbraco has different membership providers for members (front end) and users (back end.) I imagine you could get away without using the provider for members, but you'd be forced to use the one for members. If this is a subsection of an existing website, you can try removing the <clear /> from the providers node in umbraco's web.config. Just guessing here, I've not tried the setup you have.
You can switch back on using the "default" asp.Net MembershipProvider without any problems, but be aware that the "Membership/Roles" functionalities in the Umbraco backoffice will probably not be working correctly...
Login issue with existing authentication system
Hi,
After a brief search in the forum I concluded that my issues has not been raised, how strange it may seem.
So I am creating a new one for this.
My issue is as follows. I have an existing webapplication that uses forms authentication and asp.net membership provider, and installed the Umbraco to use as cms for a subsection of the application.
However, the install overrides my previous configuration for login (changing the login form i.e) and replaces my configured membership and role provider to use its own.
Now, the umbraco database is separate from my application database, and thats how I want it. Umbraco editors in its own database and my existing users in my existing database.
Since Umbraco changes my authentication configuration, my application does not work anymore, since all authentication is dispatched to its own login form, and seemingly to its own membership database.
So my question is, and its decisive for my evaluation, if Umbraco requires that all users are in the same membership database.
If so, what is the best solution: moving my existing user to the umbraco database(I rather not), or create the roles that umbraco needs i my existing database and use my old membershipprovider?
best regards,
Umbro
umbraco has different membership providers for members (front end) and users (back end.) I imagine you could get away without using the provider for members, but you'd be forced to use the one for members. If this is a subsection of an existing website, you can try removing the <clear /> from the providers node in umbraco's web.config. Just guessing here, I've not tried the setup you have.
Here is a project that will allow you to create members from an existing data source:
http://our.umbraco.org/projects/developer-tools/cmsimport
Hi Ai,
You can switch back on using the "default" asp.Net MembershipProvider without any problems, but be aware that the "Membership/Roles" functionalities in the Umbraco backoffice will probably not be working correctly...
There was another post related to a similar issue, you can check it at http://our.umbraco.org/forum/developers/api-questions/11351-Umbraco-membership-alongside-standard-aspnet-membership
Cheers,
Michael.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.