Open subes opened 4 years ago
Could also provide client integration test cases for OpenID Connect (requires new spring-security client module), OAuth 2.0 (requires new security client module) and SAML 2.0 (already exists as invesdwin-context-security-saml module).
Keycloak should be configurable to use a database as provided by invesdwin-context-persistence-jpa or a LDAP as provided by invesdwin-context-security-ldap-sever (which will likely be split into two separate modules, one for apacheds, another for OpenDJ).
See: https://github.com/subes/invesdwin-context-security/issues/1
It will be better to embed keycloak as a docker image into test cases instead of trying to embed it in the classpath: https://www.testcontainers.org/test_framework_integration/junit_5/
keycloak is easily embeddable: https://www.baeldung.com/keycloak-embedded-in-spring-boot-app
provide integration similar to ApacheDS so it can be turned on/off via annotation in unit tests.
This can then be used for authentication example projects in invesdwin-context-client with some js frontend framework.