Greg Lindstrom
08/18/2026, 2:22 PMkapa.ai
08/18/2026, 2:22 PMauthenticationId field exists on the user object and must exactly match (case-sensitively) the sub claim provided by your IdP. [Auth ID matching]
• In several support cases, the Auth ID was found to be missing or incorrect, and GoodData Support had to update it directly — suggesting it may not be straightforwardly editable from the UI after creation. [Auth ID fix]
However, the knowledge sources do not explicitly describe whether the Auth ID is visible or editable in the UI after user creation, nor do they document an API endpoint specifically for retrieving it for auditing purposes.
Recommended next steps:
1. Check the GoodData Users API — the authenticationId property exists on the user object in the SDK/API, so it may be retrievable programmatically via the REST API or GoodData Python SDK even if it's not shown in the UI. [authenticationId property]
2. Contact GoodData Support to confirm whether the Auth ID is visible/editable post-creation in the UI, and what the recommended approach is for auditing Auth IDs across your users. image 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed.Shamil Akhmadyshev
08/18/2026, 2:46 PMGreg Lindstrom
08/19/2026, 6:49 PMShamil Akhmadyshev
08/19/2026, 7:07 PMGreg Lindstrom
08/19/2026, 7:24 PM