Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,553,083
Community Members
 
Community Events
184
Community Groups

Allow domain users to be users in crucible

We have been using fisheye/crucible for a couple years and are gettting back into JIRA, plus Confluence and want to utilize with Crowd with them for SSO via our Active Directory. Last week we edited the permission scheme (agile) so all users can view reviews. We are having issues creating reviews in crucible - we have a web-hook setup that executes a script in our code to create reviews automatically and it has worked fine with built-in accounts. Now after we have login with our Active Directory accounts and setup our tokens we cannot get reviewers for a given project. Any ideas on which permissions we need to setup?

2 answers

1 accepted

1 vote
Answer accepted

Please see my reply to Paulo above

0 votes
PauloP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 31, 2012

Hi Aelliott

If this process is properly running with a built-in (Crucible) account, you should be able to keep using it. However, just be sure that you don't have this same user account in AD side.

The application will try to find this user in AD. If not found, the server will look for the account in the internal directory, so bult-in account.

For further details, I would suggest to raise a ticket at support.atlassian.com

Cheers,

Paulo Renato

Thanks for your response.

We believe we have a solution for this - we ditched the Agile Permission Scheme and used the default after updating the roles so that most roles allow all user types (Reviewer, Creator, Author, Moderator (though we aren't using a Moderator)) to handle most permissions except the ones it wouldn't really apply (e.g. Create [review]). Then we had to update the script run by the web-hook to use our accounts from AD.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events