Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • I have created a field configuration and field configuration scheme for a JIRA project. This configuration and scheme is assigned *only* to one project. BUT, when I create a custom field, the new custom field ends up in all of my projects. Suggestions?

Unable to login with LDAP active directory after upgrade to 8.22.3

Michael DeGroot
June 6, 2022

I upgraded Jira Core to 8.22.3 and I am now unable to login with my active directory accounts.  

I logged in with the recovery account and test the remote directory connection.  All of the steps complete except the user authentication.  I get this error:

 

Test user can authenticate : Failed
org.springframework.transaction.CannotCreateTransactionException: Could not create DirContext instance for transaction; nested exception is org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090439, comment: AcceptSecurityContext error, data 57, v4563]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090439, comment: AcceptSecurityContext error, data 57, v4563]
For more information regarding LDAP error codes see Troubleshooting LDAP Error Codes.
I tried resetting my service account's password with no effect.  The user passwords are correct and can authenticate as regular logins.

2 answers

0 votes
Theinvisibleman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 17, 2014

In addition to what Nic mentioned, when creating a custom field, you can also configure which projects and/or issue types it would appear in (as part of the custom field context). Further info on this here : https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field

0 votes
Nic Brough -Adaptavist-
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 Champions.
February 17, 2014

A field config scheme automatically includes all fields.

When you add a new field, it is defaulted to "visible" in all the field configurations you've effectively added it to.

So, the only suggestion I've really got is "when you add a new field, remember it's going to appear in all the field configs and remember to edit them all"

Sascha Mareth
September 10, 2014

We noted this as well I had hoped there is a way to invert this behavior. We have several field configurations and whenever I insert one specific field I have to unhide it everywhere to stay clean. (Even if it is considered in screens and types etc.) The other way around would be better in our case:-)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events