Overview
In Khoros Communities Aurora version 25.11, custom endpoints that execute GraphQL mutations using the graphqlAdmin client can fail because the request is evaluated as if it is coming from a logged-out / unauthenticated user.
When this happens, the endpoint may return a 500 response and your GraphQL payload may include errors such as:
UserRef[id=-1] does not have access to RequiredPermissions...User must be registered
This issue is called out in the Khoros Communities 25.11 Release Notes and is fixed in 25.12 (see Khoros Communities 25.12 Release Notes).
Resolution
- Confirm you are running Aurora 25.11. If you are not sure which version you are running, you can verify this either from the admin UI or by calling this URL:
https://YOUR_COMMUNITY_URL/t5/s/status/version -
Upgrade to Aurora 25.12 (or later). This upgrade contains the fix for the 25.11
graphqlAdminregression. (How to Manage Instance Upgrade Settings with the AI assistant) - Re-test the endpoint after the upgrade and confirm that the GraphQL mutation succeeds and no longer returns logged-out/anonymous permission errors.
Note: If you are already on 25.12+ and are still seeing failures, this is likely a different problem (for example, the logged-in user truly does not have the required permissions for the operation). In that situation, contact Support with the details below.
What to provide to Support (if the issue persists)
- Community URL(s) where the issue occurs
- The endpoint URL you are calling (or the endpoint name/path)
- The GraphQL operation name / mutation name being executed
- A sample request (headers + body) and the full error response
- The approximate timestamp of a failing request (include timezone)
- Your current Aurora version (for example, 25.11 or 25.12)
Frequently Asked Questions
-
Q1. How do I know if this known issue applies to me?
- A1. If you are running Aurora 25.11 and your custom endpoint uses
graphqlAdmin, you may see 500 errors where the GraphQL error message indicates the request is being evaluated as logged out/anonymous (for example,UserRef[id=-1]orUser must be registered). -
Q2. Is there a workaround in Aurora 25.11?
- A2. The recommended resolution is to upgrade to Aurora 25.12 or later. If upgrading is not currently possible in your environment, contact Support and provide the details listed above so the team can advise on next steps.
-
Q3. Where is the fix documented?
- A3. The issue is noted in the Khoros Communities 25.11 Release Notes, and the fix is listed in the Khoros Communities 25.12 Release Notes.
Ciprian Nastase
Comments