-
Notifications
You must be signed in to change notification settings - Fork 53
We need to start to consider the plan for adopting the keycloak #449
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
Comments
This PR #458 is a good reference, feel free to copy the code from it. |
Spoke to @yunchipang - she mentioned Daniel will take on this project (as confirmed by Cynthia) this issue will be closed after he adds integration tests to pr#458 where features have already been implemented. |
Spoke to Daniel to chase up on this |
Daniel confirmed that he had to do some work on the API beyond just the integration tests, but it's all coming together |
@z3347906 Any indication on when this will be complete? |
Spoke to @daniel - multi stage project (api added to cloak, release to data environment) api implemented and deployed -> can be closed. However, need to work on the wallet app & wallet admin client with app developer -> need to discuss with @dadiorchen & @daniel |
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 text was updated successfully, but these errors were encountered: