Avinash Pandey
12/23/2025, 7:12 AMkapa.ai
12/23/2025, 7:13 AMauthId (or Auth0 ID) linked to the OIDC provider, which caused login failures and prevented password-reset emails from being sent. [[User re-added, no login](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1736266672934719); [Auth0 id missing](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1739395018610799)] - In several cases, Support updated the user’s authId or recreated the user in Auth0, after which the user could log in by using “Forgot password” again. [[Auth0 id fix](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1739395018610799); [Auth0 recreation](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1748500430362489)] 2. User deleted or only partially recreated - Sometimes the user was deleted from the domain and then re-added only in the GoodData organization, but not in the OIDC provider, which led to the same “invalid username or password” and no reset email. [[Deleted user must be re-invited](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1746434978385639); [Recreated without Auth ID](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1736266672934719)] 3. Transition to own OIDC (professional/paid tier) - For some paid/professional environments, the domain is preconfigured for you to move to your own OIDC. In that transition state, invitation/password-reset emails tied to GoodData’s managed OIDC may stop working, and new/updated users must be provisioned by GoodData Support until your own OIDC is in place. [[Transition to own OIDC](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1748987524824719); [Professional-tier transition](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1748500430362489)] Because I don’t have access to your specific domain or user record, I cannot see which of these applies to you. The knowledge sources also don’t provide a self-service way to repair a missing `authId`—in all examples, GoodData Support fixed it from their side. Recommended next steps 1. Contact GoodData Support (or your internal GoodData admin) and provide: - Your GoodData hostname (e.g. <http://yourcompany.cloud.gooddata.com|yourcompany.cloud.gooddata.com>) - The email you use to log in - A note that: - You get “invalid username or password” - You do not receive the “Forgot Password” email - You suspect your user may be missing or have an incorrect authId / Auth0 ID, based on similar resolved cases. 2. Ask them specifically to: - Check whether your user exists both: - in the GoodData organization, and - in the configured OIDC/managed Auth0 - Verify or correct your authId / Auth0 ID, or recreate your user in the OIDC if needed. [[Auth0 id fix](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1739395018610799); [Broken user deleted & recreated](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1748500430362489)] 3. After Support confirms the fix, go again to your GoodData login page and use “Forgot Password” to set a new password, then log in with that password. This is how all similar cases were resolved. [[Resolution steps](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1736266672934719)] If you can share (with Support, not here) whether your organization uses GoodData’s managed OIDC or your own OIDC, that will also help them pinpoint the exact fix more quickly.Mauricio Cabezas
12/23/2025, 7:35 AMAvinash Pandey
12/23/2025, 7:50 AMMauricio Cabezas
12/23/2025, 8:00 AMAvinash Pandey
12/23/2025, 8:31 AMAvinash Pandey
12/23/2025, 8:31 AMMauricio Cabezas
12/23/2025, 9:45 AMAvinash Pandey
12/23/2025, 10:26 AMMauricio Cabezas
12/23/2025, 10:54 AMMauricio Cabezas
12/23/2025, 1:26 PMAvinash Pandey
12/23/2025, 2:04 PM