Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support reset password flow for CCloud connections #310

Open
flippingbits opened this issue Jan 28, 2025 · 0 comments
Open

Support reset password flow for CCloud connections #310

flippingbits opened this issue Jan 28, 2025 · 0 comments
Labels
enhancement New feature or request ga Should be handled before GA good first issue Good for newcomers

Comments

@flippingbits
Copy link
Contributor

We delegate the authentication with CCloud to the CCloud UI. Upon completion of the authentication flow, the CCloud UI redirects the user to the sidecar-exposed callback page available at http://localhost:26636/gateway/v1/callback-vscode-docs.

If the user decides to reset their password during the authentication flow, the CCloud UI will redirect the user to the URLhttp://localhost:26636/?email=...&success=true&message=... after completing the reset password flow.

At the moment, we render the error Resource not found in this case because we don't handle the / route. We should handle the redirect URI used by the reset password flow and redirect the user to the VS Code extension so that the extension can prompt the user to restart the authentication flow and sign into CCloud using their new password.

cc @shouples @noeldevelops this will require some work on the extension side and might require further discussion

@flippingbits flippingbits added enhancement New feature or request ga Should be handled before GA good first issue Good for newcomers labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ga Should be handled before GA good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant