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

Update to newest Version #1

Open
geloro94 opened this issue Sep 13, 2022 · 1 comment
Open

Update to newest Version #1

geloro94 opened this issue Sep 13, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@geloro94
Copy link

The current version of feasibility-auth is not compatible with feasibility-gui (13.09.2022) Please update the configuration to match the Roles used by the default configuration of feasibility-gui.

Idea is that this container can be used with docker-compose up in a development environment to work with the feasibility-gui and feasibility-backend. Accordingly the port should be set to 8080

@geloro94 geloro94 added the bug Something isn't working label Sep 13, 2022
michael-82 added a commit that referenced this issue Sep 14, 2022
- Update the initial-realm-dev.json file to change all occurrences from "codex" to "feasibility"
- user passwords in dev file are still "codex"
michael-82 added a commit that referenced this issue Sep 14, 2022
- change user passwords to "feasibility"
michael-82 added a commit that referenced this issue Sep 14, 2022
- rename keycloak service to "auth"
@geloro94
Copy link
Author

@juliangruendner after the MII Symposium, change all (backend, frontend, auth) to match the fdpg keyloak realm and users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants