Login issues using "Atlassian Jira" User Directory

[zooom productions]

Hi all

we use Jira for the user management for Jira and Confluence (- both running on our own server.
After an update the Jira Server disappeared and Jira used the internal user directory only. This caused Confluence to deny all login attempts.

We added the "Atlassian Jira" again as a user directory (and also the app) and moved it to the 1st position (but we left the Internal Directory untouched) - but now we can not even log into Jira any more...
We had a look into the database, and there are still users.

We are not able to login into Jira or Confluence using the recovery user as well...

I'm not sure if we are running on the very latest version of Jira

In the log we found

2020-05-13 16:18:05,096+0200 Caesium-1-4 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2020-05-13 16:18:05,107+0200 Caesium-1-4 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2020-05-13 16:18:05,107+0200 Caesium-1-4 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was not completed, falling back to a full synchronisation
2020-05-13 16:18:05,107+0200 Caesium-1-4 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL

What can we do?

Any ideas?

[Ed Letifov _TechTime - New Zealand_]

Is this Jira and Confluence both connected to some other Jira? Or Jira and Confluence, with Confluence connected to Jira for user management?

The fact that "Jira used Internal directory only after upgrade" is a bit confusing as in the 2nd case it would have used the internal only always. It would be Confluence that would have two - it's own internal and Jira's one. Did you add Jira directory into Jira?

Anyway, first you need to resolve your logging to Jira issues, then deal with Confluence, since it is connected to Jira. Is there any reason why you are asking for support on a community forum instead of going to Atlassian Support: https://support.atlassian.com/

[zooom productions]

Hi, and many thanks
I reached out the the support but did not get any answer.

But: please see this issue as closed. We found the issue in the connection between Jira / Confluence. It was a wrong configuration after the update. We needed to roll back for a day through our backup and it works again.

many thanks
Hannes

[Ed Letifov _TechTime - New Zealand_]

I am glad it works for you :)