-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feat: kc gold integration #2135
Conversation
c8792a0
to
2b981ae
Compare
|
||
-- As we migrate to keycloak gold, we reject all ciip_user_organisation permissions, | ||
-- to ensure user accounts don't inherit someone else's access permissions (on the odd chance of a changed email address). | ||
update ggircs_portal.ciip_user_organisation set status='rejected'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
be clear when we deploy to prod, communicate with business area
schema/deploy/types/jwt_token.sql
Outdated
@@ -3,30 +3,6 @@ | |||
|
|||
begin; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also be a 001
migration for the same reason as above
6e582ec
to
8769427
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 Awesome! Looks good to me.
Things I checked:
- Non-idempotent sqitch changes were made to follow our numbered migration format
- I was able to log in to the app
- My user was created in the db using the idir guid and email address from kc
- My user was updated in the db using the idir guid and email address from kc (after I manually changed my uuid and reset the can update flag to true)
No description provided.