BugNet Authentication question (CS2008) - General discussion

BugNET Forums

Forum General General discuss... BugNet Authentication question (CS2008)

8/13/2008 4:21 PM

	emigrating
4 posts

BugNet Authentication question (CS2008)

Perhaps this is already easily achievable, in which case please point me in the right direction :)

Basically, I would like to use BugNET as an issue tracker for a handful of projects I'm involved in - all of these projects are using Community Server 2008 as their 'front-end' website with a large number of registered users assigned various roles (for example BetaTester). What I'm looking for is a way for BugNET to tap into the CS user authentication and allow users from specific roles access to the issue database. For example, all users assigned to the BetaTester role should be able to add new issues to BugNET, all Contributer members should be able to take ownership and complete issues logged and so on.

So I guess the question is; is there a way to point BugNET to use third-party authentication without rewriting too much of the code? Oh, all the CS sites are using Forms authentication btw.

8/14/2008 12:30 PM

	smoss
108 posts
www.orbitsolutions.co.za

Re: BugNet Authentication question (Community Server S2008)

Here is something dead easy you can try and it will probably work.

You will (temporarily) lose all user accounts and history, so it best to back up and run off a clean BugNET database.

Open your web.config for BugNET in IIS (Under ASP.NET Tab, Edit Configuration button)

You are now in "ASP.NET Configurations Settings" Dialog (editing your web.config file)

Step 1:

Create a new connection string pointing to your Community Server SQL database. (This is where your users for Community Server is stored)

Step 2:

Under the Authentication tab, Choose to manage providers. In this case our default provider is "AspNetMembershipProvider"

Click on "Manage Providers"

Step 3:

Edit the connection string property of AspNetMembershipProvider to the connection string you created in Step 1.
Edit the Application Name to be the same as Community Server.

Step 4:

Ok. Open web.config for both Community Server and BugNET.
Copy over your MachineKey setting in Community Server's web.config file and overwrite the machine key it in the BugNET web.config. This will make the encryption keys for Community Server and BugNET the same.

Everything should be fine. BugNET will get it's authentication from Community Server user base.

8/14/2008 3:58 PM

	emigrating
4 posts

Re: BugNet Authentication question (Community Server S2008)

Thanks, that was my initial plan, but it didn't work out the box so figured I'd check. Now that you suggested the same thing I've tried again (and spent some more time on it - there were special considerations due to IIS7 and server-level configurations) and you're right it does work :)

Now, is there an easy way of getting at the CS Roles? BugNET is still showing it's own internal Roles but it seems I have to manually go in and add each and every user to the correct one - I would love if I could just tell BugNET that BetaTester == {project} Reporter and all the users in that CS Role would have the correct permissions straight away.

8/15/2008 2:09 AM

	smoss
108 posts
www.orbitsolutions.co.za

Re: BugNet Authentication question (Community Server S2008)

As far as I know there wont be a way to get the roles over. Davin ideas ?

8/15/2008 11:53 AM

	admin
634 posts
bugnetproject.com

Re: BugNet Authentication question (Community Server S2008)

smoss wrote

As far as I know there wont be a way to get the roles over. Davin ideas ?

BugNET's user roles and permissions are pretty specialized and I don't see an easy way to get the roles to align.

Davin Dubeau
BugNET - Core Developer

Page 1 of 1

Forum

General

General discuss...

BugNet Authentication question (CS2008)

Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.