From f16ac3237d52be4f8492da9ddbdcab1a62c08e73 Mon Sep 17 00:00:00 2001 From: Ilya Buziuk Date: Tue, 12 Apr 2022 09:57:13 +0200 Subject: [PATCH] fix: always bind AdminPermissionInitializer regardless of the auth mode Signed-off-by: Ilya Buziuk --- .../main/java/org/eclipse/che/api/deploy/WsMasterModule.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assembly/assembly-wsmaster-war/src/main/java/org/eclipse/che/api/deploy/WsMasterModule.java b/assembly/assembly-wsmaster-war/src/main/java/org/eclipse/che/api/deploy/WsMasterModule.java index 48f640c2a8..c9b94f280e 100644 --- a/assembly/assembly-wsmaster-war/src/main/java/org/eclipse/che/api/deploy/WsMasterModule.java +++ b/assembly/assembly-wsmaster-war/src/main/java/org/eclipse/che/api/deploy/WsMasterModule.java @@ -406,10 +406,10 @@ public class WsMasterModule extends AbstractModule { } else { install(new KeycloakModule()); install(new KeycloakUserRemoverModule()); - bind(AdminPermissionInitializer.class).asEagerSingleton(); bind(RequestTokenExtractor.class).to(ChainedTokenExtractor.class); } + bind(AdminPermissionInitializer.class).asEagerSingleton(); install(new MachineAuthModule()); // User and profile - use profile from keycloak and other stuff is JPA