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.

Sign up for GitHub

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

Jump to bottom

We need to start to consider the plan for adopting the keycloak #449

Open

dadiorchen opened this issue Dec 20, 2023 · 1 comment · May be fixed by #458

Assignees

Collaborator

dadiorchen commented Dec 20, 2023

Currently, keycloak has been deployed to prod/dev, so let's try to figure out how do we integrate the wallet api with keycloak.

So thoughts on my side:

The integration seems not so complcated, we just need to bind the user id from keycloak, and let keycloak delegate all the auth & auth stuff.
But because the current user system are used for clients, we need to do a smooth migration and maybe let them work parallelly for a while, and consider the transition steps/plan.

dadiorchen added this to Auth system with Keycloak + Ambassador

dadiorchen moved this to 🌱 Backlog in Auth system with Keycloak + Ambassador

dadiorchen linked a pull request

that will close this issue

Keycloak integration #458

Open

6 tasks

dadiorchen added this to Wallet mobile app

dadiorchen assigned yunchipang

Collaborator Author

dadiorchen commented Feb 8, 2025

This PR #458 is a good reference, feel free to copy the code from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment