Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
1.6
-
Crowd integrated with Active Directory and Confluence
-
Severity 2 - Major
-
Description
Hello everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Crowd team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Crowd Team
Having Crowd integrated with Confluence and the following Directories assigned to the application:
-> Internal: Containing confluence-users group
-> AD-Connector: Containing a confluence-users group and its nested group, nested_to_confluence-users
Group nested_to_confluence-users contains user nested_user
This user will be able to login into Confluence only if directory AD-Connector is the fist on the Applications Directories list.
If the Internal directory is the first of the list, the user can try to login into Confluence but will receive a Not Permitted message.
(See attached screenshot)
Attachments
Issue Links
- mentioned in
-
Wiki Page Loading...