<![CDATA[OAuth Complete Registration functionality breaks the authorization flow after upgrading to version 1.59.1]]>Flow Before Version 1.59.1
  1. Open the registration page.
  2. Click "Google" (or another OAuth identity provider).
  3. Authorize with Google.
  4. Get redirected to the provided URL (my app).

This flow was simple and straightforward.

Flow After Version 1.59.1

  1. Open the registration page.
  2. Click "Google" (or another OAuth identity provider).
  3. Authorize with Google.
  4. The /oauth2/complete-registration page opens.
  5. The user is forced to provide a password (Why? The user wants to log in with Google and shouldn't need a password at this point. We don't need it either).
  6. The user clicks "Submit" on the complete registration page.
  7. The Sign In page opens (Why? The user should already be signed in).
  8. The user has to sign in again (Why? How do we explain that this is expected behavior and not a bug, especially right after a successful registration?).
  9. Finally, the user is redirected to the provided URL (my app).

This adds unnecessary complexity and confusion. How can we avoid the complete registration page and redirect the user straight to the app? It's acceptable for the user to see the complete registration page, but it is not acceptable to force them to sign in again.

]]>https://fusionauth.io/community/forum/topic/3048/oauth-complete-registration-functionality-breaks-the-authorization-flow-after-upgrading-to-version-1-59-1RSS for NodeFri, 17 Jul 2026 20:11:14 GMTMon, 25 Aug 2025 07:03:26 GMT60<![CDATA[Reply to OAuth Complete Registration functionality breaks the authorization flow after upgrading to version 1.59.1 on Mon, 15 Sep 2025 17:40:15 GMT]]>FYI, this was fixed in 1.60.0, per the release notes.

In version 1.59.0 the password is now optional when creating or updating a user.

When returning from a third-party login, a user may be prompted to complete registration by entering a password when self-service is enabled and is configured to require a password.

This was unintended and has been corrected.

https://fusionauth.io/docs/release-notes/

Tracking issue: https://github.com/FusionAuth/fusionauth-issues/issues/3159

]]>https://fusionauth.io/community/forum/post/8372https://fusionauth.io/community/forum/post/8372Mon, 15 Sep 2025 17:40:15 GMT<![CDATA[Reply to OAuth Complete Registration functionality breaks the authorization flow after upgrading to version 1.59.1 on Tue, 26 Aug 2025 13:18:05 GMT]]>@atabakov Can you please share the settings for the application in that Admin UI? Please do not include any secrets.

]]>https://fusionauth.io/community/forum/post/8347https://fusionauth.io/community/forum/post/8347Tue, 26 Aug 2025 13:18:05 GMT