Hi Team, I followed these steps these steps to migrate the entire configuration to another environment gooddata.ai/docs/…/backups#… and now users with accounts in the old environment and the new environment cannot login. Login fails with incorrect password and the forgot password is not sending emails. The environments are using the internal IDP. Any help would be appreciated.

This is a known issue that occurs after migrating an organization to a new environment. Based on the knowledge sources, here's what's likely happening and what you should do: What's Likely Happening When you migrate an organization using the declarative API, the OIDC client secret is not included in the exported layout. If the

oauthClientSecret

field is missing or invalid in the target environment, users will not be able to log in. [Migrate to Another Environment] Additionally, from similar community cases, after environment migrations or authentication configuration changes, users can end up with a missing or broken

authId

— their account exists in GoodData but is not properly connected to the authentication layer, causing: • "Invalid username or password" errors • No password reset emails being delivered Recommended Steps 1. Check the migrated organization layout — Verify that the

oauthClientSecret

for your internal IdP was provided in the JSON before the PUT request. If it was left blank or used a placeholder, authentication will not work until it is configured. [Migrate to Another Environment] 2. Contact GoodData Support and provide: ◦ Both hostnames (source and target environments) ◦ Affected users' email addresses ◦ A description of the migration you performed and the symptoms (login failure + no password reset emails) ◦ Ask them specifically to: ▪︎ Verify the OIDC/IdP configuration is correct in the target environment ▪︎ Check whether affected users have valid

authId

values and fix any that are missing or mismatched 1. After Support confirms the fix, have affected users go to the new environment's login page, click "Forgot Password?", and use the reset link to set a new password. > Important: There is no self-service way to repair missing

authId

values or broken OIDC configuration — these require GoodData Support to resolve on the backend. 👍 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.

Hey Keith, pls forward the details specified by AI above to support@gooddata.com and we will help out.

Hey @Jakub Kopecky, I have sent the details via email

Thanks Keith, we will continue with the dialogue in the ticket