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

Keycloak server configuration #5436

Closed
skabashnyuk opened this issue Jun 22, 2017 · 1 comment
Closed

Keycloak server configuration #5436

skabashnyuk opened this issue Jun 22, 2017 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@skabashnyuk
Copy link
Contributor

We need to find answers for:

  1. Proper realm and client configuration on keycloak server. Depends on Eclipse Che application authentication #5435 Authentication on workspace agent #5434
  2. The way how to introduce initial configuration from 1. when we use Eclipse Che docker CLI. It could be either database backup or import of realm configuration.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/platform labels Jun 22, 2017
@skabashnyuk skabashnyuk mentioned this issue Jun 22, 2017
25 tasks
@skabashnyuk
Copy link
Contributor Author

Initial config added here 8defbf4 and here 8908564

We have

  1. Master realm with default user admin, password admin. Can manage realms
  2. Che ream with default user admin, password admin. Can't manage realms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

No branches or pull requests

1 participant