Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Duplicate
Priority: Highest
Fix Version/s: None
Affects Version/s: 2.3.4
Component/s: Accounts (Signup, Invite, Login, Logout, Reset Password)
Labels:
- affects-server
- publicsignup

Bug Fix Policy:
View Atlassian Server bug fix policy

Description

I have two directories. "Jira Internal Directory" and "Atlassian Crowd Directory".

The internal directory is at the "top" and is the default directory. This way, when customers self sign-up, their accounts are created in the jira directory (default directory), not the crowd directory.

When following the instructions to enable SSO by changing the Authenticator

Users can no longer authenticate to the "Internal Jira Directory" because the authenticator doesn't check the internal directory.

Attachments

Issue Links

duplicates

JSDSERVER-1244 Create a Crowd SSO authenticator that will allow Customers to be authenticated from the local directory

Gathering Interest

is related to

JSDSERVER-1717 Customers Cannot Login if using Crowd Server and closed Application

Closed

CWD-2417 CROWD - JIRA integration does not synchronize custom user attributes / LDAP attributes

Long Term Backlog

JRASERVER-42418 Allow Internal users to login with SSO enabled

Gathering Interest

JSDSERVER-1716 Directory for Customers

Gathering Interest

relates to

JSDSERVER-1052 Crowd does not recognize agent based pricing for Service Desk Customers

Closed

(1 relates to)

Activity

People

Assignee:: Kha Nguyen (Inactive)

Reporter:: James Rogers

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 30/Mar/2015 3:58 PM

Updated:: 27/Mar/2019 5:47 AM

Resolved:: 31/Mar/2015 4:04 AM

Customers Cannot Login with SSO Enabled