Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

running JIRA + Crowd as Docker-Containers - Login at JIRA is possible but shown as not synchron


Hello together,


we are running Crowd + Confluence + Jira (Core+Software+ServiceManagement) as Docker-Containers.

Login at all Applications works via Users administrated via Crowd and is shown correctly at Confluence (= last login + synchronised).

The Login at Jira works via Users administraded via Crowd too - but is not shown correctly at Jira (> last login = never + never synchronised or last time of sync. = technical fieldnames and not date/time).

Any help would be great!01 - nie angemeldet.png02 - noch nie synchronisiert.png03 - Ausgabe letztmalig synchronisiert mit technischen Feldbezeichnungen statt Startzeit und Dauer als Zeitangabe.png04 - Crowd - user - kann sich angeblich bei keiner Anwendung anmelden.png

= admin-user exists as member of all needed groups, but is not visible under "the user can authenticate with the following applications" ... while login at all Applications works

05 - installierte Anwendungen.png06 - user wird bei allen Anwendungen ausgewiesen.png07 - user gehört allen gewünschten Gruppen an.png

1 answer

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 29, 2021

Hi - Webmaster 

did you try to put into the debug mode for next package com.atlassian.crowd ? 

then you can see what's happened during authentication

At first - many thanks for your response!


The only tool we used in this context until today is the Log-Analyzer - but - without any useful hint/s.


If thinking about the debug mode ... I have a problem how to enable it via docker.

Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 01, 2021

Could you log int into container and then double check in {jira_home}/logs/atlassian-jira.log, please?

docker exec -it <CONTAINER_ID> /bin/sh

Please excuse my delayed response.

We do not find any helpful hint inside atlassian-jira.log and also it seems to be not possible to insert the full Log-Content into this community-dialogue.

It seems, that the User-Directory at Crowd is write-protected when trying to access from Jira.

Otherwhise i am absolutely shure that while setup I allowed read+write according to that User-Directory. Now it is not editable. Also deleting + fresh setup brings that connection not to work.

2021-05-01 17:06:25,005+0000 Caesium-1-1 ERROR ServiceRunner [] Error occurred while refreshing the cache for directory [ 10100 ].
com.querydsl.core.QueryException: Caught PSQLException for insert into public.cwd_synchronisation_status (directory_id, sync_start, sync_status, status_parameters, id)
values (?, ?, ?, ?, ?)
at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(
at com.querydsl.sql.Configuration.translate(
at com.querydsl.sql.dml.SQLInsertClause.execute(
at com.atlassian.jira.database.IdGeneratingSQLInsertClause.executeWithId(
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizDirectorySynchronisationStatusDao.lambda$add$1(
at com.atlassian.jira.database.DefaultQueryDslAccessor.lambda$executeQuery$0(
at com.atlassian.jira.database.DatabaseAccessorImpl.lambda$runInTransaction$0(
at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(
at com.atlassian.jira.database.DatabaseAccessorImpl.runInTransaction(
at com.atlassian.jira.database.DefaultQueryDslAccessor.executeQuery(
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizDirectorySynchronisationStatusDao.add(
at com.atlassian.scheduler.core.JobLauncher.runJob(
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(
at com.atlassian.scheduler.core.JobLauncher.launch(
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(
Caused by: org.postgresql.util.PSQLException: ERROR: could not read block 0 in file "base/16389/27664": read only 0 of 8192 bytes
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
at org.postgresql.core.v3.QueryExecutorImpl.processResults(
at org.postgresql.core.v3.QueryExecutorImpl.execute(
at org.postgresql.jdbc.PgStatement.executeInternal(
at org.postgresql.jdbc.PgStatement.execute(
at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(
at com.atlassian.jira.ofbiz.sql.PreparedStatementWrapper.executeUpdate(
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.lambda$executeUpdate$7(
at com.atlassian.diagnostics.internal.platform.monitor.db.DefaultDatabaseDiagnosticsCollector.recordExecutionTime(
at com.atlassian.jira.diagnostic.connection.DatabaseDiagnosticsCollectorDelegate.recordExecutionTime(
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.executeUpdate(
at com.querydsl.sql.dml.SQLInsertClause.execute(
... 24 more

2021-05-01 16:55:25,985+0000 http-nio-8080-exec-8 ERROR st******.a********* 1015x785x1 17rhz48, /secure/admin/WebSudoAuthenticate.jspa [] com.atlassian.crowd.exception.ApplicationPermissionException: Not allowed to update user attributes 'st******.a*********' in directory 'Crowd'.
com.atlassian.crowd.exception.OperationNotPermittedException: com.atlassian.crowd.exception.ApplicationPermissionException: Not allowed to update user attributes 'st******.a*********' in directory 'Crowd'.
at com.atlassian.crowd.embedded.core.CrowdServiceImpl.setUserAttribute(
at com.atlassian.crowd.embedded.core.CrowdServiceImpl.setUserAttribute(
at com.atlassian.jira.web.action.admin.WebSudoAuthenticate.doValidation(

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events