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

OAuth change to use keycloak #11

Open
a20688392 opened this issue Apr 14, 2024 · 0 comments
Open

OAuth change to use keycloak #11

a20688392 opened this issue Apr 14, 2024 · 0 comments
Assignees

Comments

@a20688392
Copy link
Collaborator

Why use KeyCloak?
It can help us integrat social ccount(e.g. google, fb, ig)

User Register:

  1. frontend -> keycloak
    Register account.
  2. keycloak -> frontend
    From request get with id_token.
  3. frontend -> backend
    Send register request with id_token to backend.
  4. backend execute request.
    Parse Token and save user's info(username, email, uid).
@a20688392 a20688392 self-assigned this Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant