Skip to content

Comments

fix: Lico still promoted as production ready solution #471#474

Merged
schweigisito merged 3 commits intomainfrom
clarify-lico-and-keycloak-usecases
Oct 13, 2025
Merged

fix: Lico still promoted as production ready solution #471#474
schweigisito merged 3 commits intomainfrom
clarify-lico-and-keycloak-usecases

Conversation

@schweigisito
Copy link
Member

This fixes bug #471 by adding some use case examples to help the admin being able to take well-founded and active action to decide for an IDP.

Copy link
Member

@rhafer rhafer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also maybe write more explicitly that lico, in the way we deploy it can only run as a single instance (i.e. no HA)

@rhafer rhafer requested review from dragotin and tbsbdr September 30, 2025 10:26
@schweigisito schweigisito requested review from rhafer and tbsbdr October 9, 2025 07:11
Copy link
Contributor

@Svanvith Svanvith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@schweigisito schweigisito merged commit 4f811af into main Oct 13, 2025
2 checks passed
@schweigisito schweigisito deleted the clarify-lico-and-keycloak-usecases branch October 13, 2025 12:08
@openclouders openclouders mentioned this pull request Oct 8, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants