You may be running into the same issue that has been reported for the CMS site: a mismatch between the Membership and Roleproviders.
Here's how to fix it:
1. Open the web.config file and add an applicationName attribute to the roleProvider like this:
2. Run the WAT by choosing Website | ASP.NET Configuration from within Visual Web Developer (with the BugBase project open of course)
3. Click the Security tab
4. Make sure the roles are there. If not, create the following roles:
5. Next, if necessary, create the user accounts:
and assign them to the appropriate roles
6. Run the site and log in with one of your accounts. Things should work as expected.
If you're lazy, you can just create the four roles and the SuperUser account, assign it to those four roles and log in and then manage the rest of the accounts through the BugBase Maintenance section.
Once you're logged in, choose Maintenance | Members. From there you can create new accounts and assign them to existing roles. This section is a nice demo of working with the Role and Membership API's and shows you how to build your own user management tool if you find the WAT to be too limited.
The Maintenance section doesn't allow you to create new roles on-line (there's no point because you would also need to write new functionality that makes use of those roles), but with the code from the Membership section, it shouldn't be too hard to figure out how to create and manage roles programmatically.
Hope this helps,
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results
and Beginning Dreamweaver MX / MX 2004
While typing this post, I was listening to: The Only One
by Limp Bizkit
(Track 9 from the album: Results May Vary
) What's This?