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
4,293,373
Community Members
 
Community Events
165
Community Groups

Directory 'Crowd Server' is not functional during authentication

after  update crowd to 5.0, 

my jira、confluence can't authentication from crowd.

and i grab the request on crowd server like this:

POST /crowd/rest/usermanagement/1/session/jDDLY8MoUNhN5UquoSo1JAAAAAAAAgABY2h5ZGFu HTTP/1.0.
X-Forwarded-Host: crowd.chydan.com.
X-Forwarded-Server: crowd.chydan.com.
X-Forwarded-For: 47.103.146.6.
Host: 47.102.106.105:8095.
Connection: close.
Content-Length: 284.
Accept: application/xml.
Content-Type: application/xml; charset=UTF-8.
User-Agent: Apache-HttpClient/4.5.5 (Java/1.8.0_321).
Cookie: JSESSIONID=AE0C8BBCA50053EA0AFA42B3199AAA69.
Accept-Encoding: gzip,deflate.
Via: 1.1 localhost (Apache-HttpClient/4.5.5 (cache)).
Authorization: Basic Y2h5ZGFuX2ppcmE6Y2h5ZGFuMjAyMQ==.
.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><validation-factors><validation-factor><name>remote_address</name><value>47.103.146.6</value></validation-factor><validation-factor><name>X-Forwarded-For</name><value>66.112.212.44</value></validation-factor></validation-factors>
##
T 172.31.185.68:8095 -> 47.103.146.6:36452 [AP] #1731
HTTP/1.1 404 Not Found.
X-XSS-Protection: 1; mode=block.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.
Content-Security-Policy: frame-ancestors 'self'.
X-Embedded-Crowd-Version: Crowd/5.0.0.
X-Crowd-User-Management-Version: 1.4.
Set-Cookie: crowd.rememberme.token=; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/crowd; HttpOnly.
Content-Type: application/xml;charset=UTF-8.
Content-Length: 147.
Date: Fri, 17 Jun 2022 11:35:39 GMT.
Connection: close.
.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>INVALID_SSO_TOKEN</reason><message>Token does not validate.</message></error>
########
T 47.103.146.6:37192 -> 172.31.185.68:8095 [AP] #1739
GET /crowd/rest/capabilities HTTP/1.0.
X-Forwarded-Host: crowd.chydan.com.
X-Forwarded-Server: crowd.chydan.com.
X-Forwarded-For: 47.103.146.6.
Host: 47.102.106.105:8095.
Connection: close.
Accept: application/json.
Content-Type: application/json.
User-Agent: Confluence-7.13.5 (14871).
Accept-Encoding: gzip,deflate.
.

##
T 172.31.185.68:8095 -> 47.103.146.6:37192 [AP] #1741
HTTP/1.1 302 Found.
X-XSS-Protection: 1; mode=block.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.
Content-Security-Policy: frame-ancestors 'self'.
Set-Cookie: crowd.rememberme.token=; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/crowd; HttpOnly.
Set-Cookie: crowd.rememberme.token=; Max-Age=0; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/crowd; HttpOnly.
Set-Cookie: JSESSIONID=134120010F99A02A4B8D15787FF99C60; Path=/crowd; HttpOnly.
Location: http://crowd.chydan.com/crowd/console/login.action.
Content-Type: text/html;charset=UTF-8.
Content-Length: 0.
Date: Fri, 17 Jun 2022 11:36:48 GMT.
Connection: close.

 

2022-06-17 19:36:38,421+0800 http-nio-8081-exec-15 ERROR anonymous 1176x216x1 17kjt73 66.112.212.44,47.103.146.6 /login.jsp [c.a.c.manager.application.ApplicationServiceGeneric] Directory 'Crowd Server' is not functional during authentication of 'hanlu.che'. Skipped

1 answer

0 votes

Hi @chehanlu_126_com ,

welcome to the Atlassian community!

First of all please try to perform a new synch on JIRA side. Please let us know if it works.

Fabio

synch is failed 

 

2022-06-17 20:11:09,232+0800 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] starting
2022-06-17 20:11:09,232+0800 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Attempting INCREMENTAL synchronisation for directory [ 10000 ]
2022-06-17 20:11:09,232+0800 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was not completed, falling back to a full synchronisation
2022-06-17 20:11:09,232+0800 Caesium-1-3 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] INCREMENTAL synchronisation for directory [ 10000 ] was not successful, attempting FULL
2022-06-17 20:11:36,400+0800 Caesium-1-3 WARN ServiceRunner [c.a.c.d.ldap.cache.EventTokenChangedCacheRefresher] Could not update event token.
com.atlassian.crowd.exception.OperationFailedException: Internal Server Error
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:536)
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:364)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.getCurrentEventToken(RestCrowdClient.java:997)
at com.atlassian.crowd.directory.RemoteCrowdDirectory.getCurrentEventToken(RemoteCrowdDirectory.java:631)
at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseAll(EventTokenChangedCacheRefresher.java:47)
at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:978)
at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:67)
at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.synchronizeDirectory(JiraDirectorySynchroniser.java:77)
at com.atlassian.jira.crowd.embedded.JiraDirectorySynchroniser.runJob(JiraDirectorySynchroniser.java:52)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
at java.lang.Thread.run(Thread.java:750)

Suggest an answer

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

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,098 views 34 44
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