Password reset redirect in "WPF" or .net MAUI #111
-
how to get the app to detect type=recovery in the fragment of the url below and display a password reset form to the user using supabase c# in "WPF" or .net MAUI ( after the user have clicked the 'reset password' in the email) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Good catch - this is a method that requires PKCE support. The gotrue team intentionally set the redirect urls to use a That is now being tracked here: #112 |
Beta Was this translation helpful? Give feedback.
-
Thank you for the update and for tracking the issue (#112). It's good to
know that PKCE support is being considered to address the use of "#" in the
redirect URLs for enhanced security. I look forward to seeing the
implementation of PKCE in the future. If there's any way I can assist or
contribute to this effort, please don't hesitate to reach out.
…On Sun, Oct 1, 2023 at 4:30 PM Joseph Schultz ***@***.***> wrote:
Good catch - this is a method that requires PKCE support. The gotrue team
intentionally set the redirect urls to use a # instead of a ? so that the
parameters passed back can only be read on the client side. A PKCE flow
gets around this, but that hasn't been implemented on our client yet
(didn't know about this functionality!).
That is now being tracked here: #112
<#112>
—
Reply to this email directly, view it on GitHub
<#111 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANKXECSIGRHKEHUZPVTAQNDX5F5ADANCNFSM6AAAAAA5NWJABE>
.
You are receiving this because you authored the thread.Message ID:
<supabase-community/supabase-csharp/repo-discussions/111/comments/7157858@
github.com>
--
MR. MELVIN MAGORO
|
Beta Was this translation helpful? Give feedback.
Good catch - this is a method that requires PKCE support. The gotrue team intentionally set the redirect urls to use a
#
instead of a?
so that the parameters passed back can only be read on the client side (so C# has a real hard time playing nice with these). A PKCE flow gets around this, but that hasn't been implemented on our client yet (didn't know about this functionality!).That is now being tracked here: #112