Synchrony logs show invalid-aud and Synchrony is not connecting to Confluence
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Synchrony will not connect to Confluence as expected after the initial setup.
The following appears in the atlassian-synchrony.log
"type":"jwt/invalid-aud","aud":"https://confluence.example.com/synchrony/v1","expected-auds":["http://confluence.example.com/synchrony"],"ns":"synchrony.sync.hub","throwable":"clojure.lang.ExceptionInfo: JWT aud property does not match expected value {:type :jwt/invalid-aud, :aud \"https://confluence.example.com/synchrony/v1\", :expected-auds [\"http://confluence.example.com/synchrony\"],Diagnosis
Environment
- Confluence Data Center 6.x
- Existing Synchrony node or cluster
Cause
This is caused by an invalid synchrony.service.url in your Synchrony service config or startup script, ending in: /v1
The synchrony.service.url ending in /v1 only belongs in the Confluence server's setenv.sh config file, not in the Synchrony config.
Resolution
- Edit the synchrony service script or start-synchrony.sh script (script location will vary), and remove the /v1 at the end of the -Dsynchrony.service.url=
Example valid synchrony.service.url in the synchrony service config:
-Dsynchrony.service.url=https://<confluence_base_url>/synchrony
- Restart the Synchrony service.