Jira sAMAccountName not truncated

[Deleted user]

Hi

We've configured a Jira user directory as an Active Directory in Read/Write mode. The username attribute of the Jira directory is set to "userPrincipalName" - because this will be the e-mail address of the user.

When a user signs up for our Jira Service Desk, the account is written to the Active Directory. The sAMAccountName is set to the same value as userPrincipalName. In general this is good, because sAMAccountName is mandatory. But the issue starts if the user has an e-mail address longer than 20 characters. The account will not be created, because this is a hard limit in Active Directory.

https://docs.microsoft.com/en-us/windows/win32/adschema/a-samaccountname

The following error message is in the Jira log:

Could not create user: verylongusername@example.com
com.atlassian.crowd.exception.InvalidUserException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 80 - 00000523: SysErr: DSID-031A124A, problem 22 (Invalid argument), data 0

Questions:

• Why does Jira the sAMAccountName not truncate to 20 characters? Is there an option to enable this?
• Is there a possibility to set the sAMAccountName to something different never exceeding 20 characters, like an internal Jira user id?

[Dario B]

Ciao @[deleted]

Welcome to the Atlassian Community!

I believe this is a known bug tracked in our system as:

• [JSDSERVER-6248] Agent or Admin users of a Service Desk project can't create new customers when using an Active Directory

As mentioned in above bug ticket, a possible workaround is to:

• First, create the user from the page ⚙ > User Management > Users > Create User
  • With this creation method, you'll be able to decide what the username attribute should be and use a string which is less than 20 characters
• Then add the user to the project customers by going to the Project's Customers page, clicking on Add Customer and using the username of the user created in the first step

Please vote for the above bug ticket and set yourself as a watched so that you will be notified in case of any update/progress. The bug will be addressed according to the Atlassian Cloud bug fixing policy.

Cheers,
Dario

[Deleted user]

Hi Dario

Yes, looks like this is the same bug.

The workaround however does not apply to our use case, because the customers perform a self service sign up and don't provide a username, they only provide their e-mail address.

Kind Regards

Claudio Spizzi

[Dario B]

Thanks for the follow-up. I have asked internally if there is any other workaround that can apply in your case. I will let you know something as soon as I will get a reply.

Cheers,
Dario

[Dario B]

UPDATE: Apparently there is no other workaround available at the moment. I am getting in touch with other internal resources to see if we can get some attention on this bug or if they can think of any other way to workaround the issue. 

[Deleted user]

Hi Dario

Thank you for your update. I've added my idea to a possible solution to the issue JSDSERVER-6248.

Would be great if this bug gets more attention. :-)

Regards Claudio

[claudiospizzi]

Hi @Dario B 

Any news on this issue? We are still waiting for a fix for this bug.

Best Regards

Claudio

[Dario B]

Hi @claudiospizzi ,

I have asked if there is any update on this and I am waiting for a reply myself. 

However, from what I can see, the bug ticket didn't get much traction (8 votes so far). So, there are chances that has not been taken into account for the time being.

I will inform you in case I get any update on this.

Have a nice weekend.

Dario