| Minimum Software Version | 8.18.10 |
| Solution(s) | Cases International ✓ Cases US ✓ Institutions ⨉ Counsel ✓ |
In some V7 environments, the Characters page may fail to load for all workspaces. When this occurs, the browser console typically shows the following error:
Failed to load resource: the server responded with a /entities/peers status of 403
This issue is caused by a configuration mismatch where Puppet has not correctly replaced the coc.key. As a result, the key used by the JWT service does not match the key configured in the entities application, leading to authorization failures when loading the Characters page.
Aligning the coc.key values between services resolves the issue.
Resolving the Characters page 403 error
Log in to the server and locate the
coc.keyused by the JWT service:ShellShow more linesOpen a second terminal session and locate the key defined in the entities application:
ShellShow more linesCompare the two key values.
- If they do not match, copy the value from
coc.key.
- If they do not match, copy the value from
Replace the existing key in
entities/application.propertieswith the value from:/mnt/data/private/jwtservice/keys/coc.keySave the changes.
Navigate to the frontend application and refresh the page.
After refreshing, the Characters page should load correctly.
Related Links
- Internal Slack reference: FD 111386
https://opus2.slack.com/archives/C4ZR2MRBJ/p1722331689057449
coc.key values are consistent across services. If the issue persists after updating the key, escalate to the platform or infrastructure team for further investigation.