-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add Ory stack configs #930
Add Ory stack configs #930
Conversation
I am seeing other PRs merge into this branch, which will be merged into dev here, is that what we want? If we merge this after merging the other PRs we will break the current flow, as they require hydra. I would say we merge into one of the two feature branches for hydra/ory |
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.
Looks good.
I have updated to use a single instance of Postgres for both Kratos and Hydra in an effort to reduce the resource load for local dev and testing.
BTW, I am getting a csrf security violation when signing up (http 403). I assume that is because the enrolment ui docker image is not up to date with you latest changes?
@Bdegraaf1234 @yatharthranjan Yes sure, I've updated it now to merge to |
e1cdee9
into
feature/ory-based-authorization
Description:
kratos
configradar-self-enrolment-ui
andhydra
mpgxvii/radar-self-enrolment-ui:latest
Checklist: