LDAP for service desk project A and public sign up for service desk project B

Brian Kelly March 25, 2018

Setting: University

Scenario:

Project A would be an IT Service Desk project that supports all active students and staff at a university. Authentication is configured with delegated LDAP authentication.

Project B is would be used as a customer service portal to respond and track questions for potential applicants.

Questions:

Is it possible to have delegated LDAP authentication for Project A and public sign up available for Project B. It looks like public signup is controlled globally at the application level but once enabled the project administrator can enable or disable public sign up.

In my scenario the project administrator would disable public sign up on Project A and enable public sign up on Project B. 

Correct?

Assuming the above is correct how would one filter LDAP customer accounts from the public sign up accounts in the users management interface? There doesn't appear to be a way to filter based on project.

 

1 answer

0 votes
Deeksha
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 19, 2018

Hi Brian,

You can configure Jira to use and prioritise user directories for signup as shown here. You can set the Internal Directory to have priority over LDAP. Although you cannot set this specifically per project, you can change who can raise requests in project settings under Customer permissions. If this is set to public, the Internal Directory will be used for login for that Service Desk portal rather than LDAP. 

However keep in mind Service Desk and Jira public signup work independently.

 

Thank you,
The Jira Service Desk Team

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events