I'm currently working on a big project where an Umbraco instans will be one part and the outher part is going to be a regular "asp.net website".
The two systems will share the same users. When I'm trying to solve the architecture I have (as I see it) two options:
1. Put users / roles in Umbraco and validate against Umbraco in my webproject 2. Put users / roles in a new custom database and write a new MembershipProvider/RoleProvider for Umbraco
I notice that workning with the Umbraco API without having it "running inside umbraco" is not that easy. Adding new users is a complex proccess with lots och reads/writes to the database, so to have my new webproject create users directly to the database seams not as a good idea.
I think I'm gonna create a custom database for users/roles and then write new providers for Umbraco. What do you guys think?
Same members in to solutions
Hi!
I'm currently working on a big project where an Umbraco instans will be one part and the outher part is going to be a regular "asp.net website".
The two systems will share the same users. When I'm trying to solve the architecture I have (as I see it) two options:
1. Put users / roles in Umbraco and validate against Umbraco in my webproject
2. Put users / roles in a new custom database and write a new MembershipProvider/RoleProvider for Umbraco
I notice that workning with the Umbraco API without having it "running inside umbraco" is not that easy. Adding new users is a complex proccess with lots och reads/writes to the database, so to have my new webproject create users directly to the database seams not as a good idea.
I think I'm gonna create a custom database for users/roles and then write new providers for Umbraco. What do you guys think?
Anyone who has haved the same challange?
// Markus, Sthlm, Sweden
I'm gonna go with the second solution. Put the membsers in a custom database and write my own providers. I'll get back to let you know my experience.
// M
I'd do the same, not only do I think it will be easier, but it'll be a more portable solution, should you choose to use another CMS in the future.
+1 for the second suggested solution
Cheers,
/Dirk
Thanks guys!
Yep I would go for your suggestion also. I''ve used this scenario for a client and it works very well.
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.