Replies: 1 comment 1 reply
-
Hi, from a technical point of view our Rest-API is built with Quarkus which supports the Open ID Connect protocol. In practice we only support Keycloak at the moment, mainly because there are higher prioritised tickets. Keycloak can be installed in any cluster and may be configured to delegate to different auth providers as well. There should be no technical blocker to integrate different auth provider directly in the future however and contributions are welcome. |
Beta Was this translation helpful? Give feedback.
-
Hello team,
The current theia-cloud on AKS supports Keycloak as the authentication feature. Is there any optional way to use AAD or other authentication server instead of Keycloak?
It seems the keycloak is the only option we can take from the log below.
20:34:20.126 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: keycloak false
20:34:20.129 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: eagerStart false
20:34:20.131 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: cloudProvider GKE
20:34:20.132 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: bandwidthLimiter K8SANNOTATION
20:34:20.133 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: appId asdfghjkl
20:34:20.133 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: serviceUrl https://service.20.119.119.99.nip.io
20:34:20.134 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Parsing args: sessionsPerUser 1
20:34:20.135 [main] INFO org.eclipse.theia.cloud.operator.Main - [init] Using org.eclipse.theia.cloud.operator.di.DefaultTheiaCloudOperatorModule as DI module
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Beta Was this translation helpful? Give feedback.
All reactions