Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

Hi @IP_org - 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.

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 [c.a.crowd.directory.DbCachingDirectoryPoller] 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(DefaultSQLExceptionTranslator.java:50)
at com.querydsl.sql.Configuration.translate(Configuration.java:459)
at com.querydsl.sql.dml.SQLInsertClause.execute(SQLInsertClause.java:445)
at com.atlassian.jira.database.IdGeneratingSQLInsertClause.executeWithId(IdGeneratingSQLInsertClause.java:71)
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizDirectorySynchronisationStatusDao.lambda$add$1(OfBizDirectorySynchronisationStatusDao.java:70)
at com.atlassian.jira.database.DefaultQueryDslAccessor.lambda$executeQuery$0(DefaultQueryDslAccessor.java:68)
at com.atlassian.jira.database.DatabaseAccessorImpl.lambda$runInTransaction$0(DatabaseAccessorImpl.java:105)
at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:74)
at com.atlassian.jira.database.DatabaseAccessorImpl.runInTransaction(DatabaseAccessorImpl.java:100)
at com.atlassian.jira.database.DefaultQueryDslAccessor.executeQuery(DefaultQueryDslAccessor.java:67)
at com.atlassian.jira.crowd.embedded.ofbiz.OfBizDirectorySynchronisationStatusDao.add(OfBizDirectorySynchronisationStatusDao.java:67)
at com.atlassian.crowd.manager.directory.InDatabaseDirectorySynchronisationInformationStore.syncStarted(InDatabaseDirectorySynchronisationInformationStore.java:120)
at com.atlassian.crowd.manager.directory.SynchronisationStatusManagerImpl.syncStarted(SynchronisationStatusManagerImpl.java:53)
at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:78)
at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:45)
at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobRunner.runJob(DirectoryPollerJobRunner.java:92)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:430)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:454)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:382)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at java.lang.Thread.run(Thread.java:748)
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(QueryExecutorImpl.java:2553)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2285)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:323)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:473)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:393)
at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:130)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
at com.atlassian.jira.ofbiz.sql.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:47)
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.lambda$executeUpdate$7(DiagnosticPreparedStatement.java:69)
at com.atlassian.diagnostics.internal.platform.monitor.db.DefaultDatabaseDiagnosticsCollector.recordExecutionTime(DefaultDatabaseDiagnosticsCollector.java:70)
at com.atlassian.jira.diagnostic.connection.DatabaseDiagnosticsCollectorDelegate.recordExecutionTime(DatabaseDiagnosticsCollectorDelegate.java:55)
at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.executeUpdate(DiagnosticPreparedStatement.java:69)
at com.querydsl.sql.dml.SQLInsertClause.execute(SQLInsertClause.java:423)
... 24 more

2021-05-01 16:55:25,985+0000 http-nio-8080-exec-8 ERROR st******.a********* 1015x785x1 17rhz48 92.196.192.141,192.168.178.25 /secure/admin/WebSudoAuthenticate.jspa [c.a.j.security.login.LoginStoreImpl] 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(CrowdServiceImpl.java:335)
at com.atlassian.crowd.embedded.core.CrowdServiceImpl.setUserAttribute(CrowdServiceImpl.java:324)
at com.atlassian.jira.security.login.LoginStoreImpl.setLong(LoginStoreImpl.java:132)
at com.atlassian.jira.security.login.LoginStoreImpl.updateLastLoginTime(LoginStoreImpl.java:109)
at com.atlassian.jira.security.login.LoginStoreImpl.recordLoginAttempt(LoginStoreImpl.java:49)
at com.atlassian.jira.security.login.RecoveryLoginStore.recordLoginAttempt(RecoveryLoginStore.java:60)
at com.atlassian.jira.security.login.LoginManagerImpl.recordLoginAttempt(LoginManagerImpl.java:340)
at com.atlassian.jira.security.login.LoginManagerImpl.authenticateWithoutElevatedCheck(LoginManagerImpl.java:205)
at com.atlassian.jira.web.action.admin.WebSudoAuthenticate.doValidation(WebSudoAuthenticate.java:125)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

335 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you