<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Maintaining OAuth&#x2F;PKCE Flow During Email Verification in FusionAuth Mobile Apps]]></title><description><![CDATA[<p dir="auto">I’m trying to fine-tune our user registration flow so that, after verifying their email, users are deep-linked back into our mobile app. Ideally, I’d like them redirected to the login redirect URI monitored by the OS so the native web browser window used for OAuth/PKCE can close automatically. Right now, this isn’t working as expected. If I hard-code my login redirect URI into the email verification template, it errors out because the OAuth/PKCE code is missing. How can I achieve this with FusionAuth?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3003/maintaining-oauth-pkce-flow-during-email-verification-in-fusionauth-mobile-apps</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 05:19:46 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3003.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 30 Jun 2025 04:46:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Maintaining OAuth&#x2F;PKCE Flow During Email Verification in FusionAuth Mobile Apps on Mon, 30 Jun 2025 04:48:31 GMT]]></title><description><![CDATA[<p dir="auto">Good question—it’s a common challenge.</p>
<p dir="auto">By default, the email verification flow breaks the OAuth/PKCE context because the user leaves the registration page to check their email and clicks a verification link. FusionAuth can’t continue the OAuth flow automatically from that email link, which is why your hard-coded redirect URI fails without the required OAuth code.</p>
<p dir="auto">A better solution is to switch your email verification strategy from <strong>Clickable Link</strong> to <strong>Form Field</strong> (under Tenant → Email → Email Verification → Verification Strategy). With this approach, users stay on the original registration page, enter the verification code from their email, and the OAuth/PKCE flow remains intact—including the authorization code. This enables seamless redirecting back into your app after verification.</p>
<p dir="auto">If you’re creating and registering users for an application at the same time, remember to also check the app-level registration verification settings under:<br />
<strong>FusionAuth Admin UI → Applications → Edit Application → Registration tab</strong>.</p>
<p dir="auto">More details are in the docs: <a href="https://fusionauth.io/docs/lifecycle/manage-users/verification/registration-email-verification" rel="nofollow ugc">Registration Email Verification</a></p>
]]></description><link>https://fusionauth.io/community/forum/post/8211</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8211</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Mon, 30 Jun 2025 04:48:31 GMT</pubDate></item></channel></rss>