Fix #4429: Authorizer module should start after ES publisher is started (#4430)

This commit is contained in:
Sriharsha Chintalapani 2022-04-23 19:17:20 -07:00 committed by GitHub
parent a4ac73e867
commit 48d39b14ee
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -121,7 +121,6 @@ public class CatalogApplication extends Application<CatalogApplicationConfig> {
registerResources(catalogConfig, environment, jdbi); registerResources(catalogConfig, environment, jdbi);
RoleEvaluator.getInstance().load(); RoleEvaluator.getInstance().load();
PolicyEvaluator.getInstance().load(); PolicyEvaluator.getInstance().load();
authorizer.init(catalogConfig.getAuthorizerConfiguration(), jdbi);
// Register Event Handler // Register Event Handler
registerEventFilter(catalogConfig, environment, jdbi); registerEventFilter(catalogConfig, environment, jdbi);
@ -130,6 +129,9 @@ public class CatalogApplication extends Application<CatalogApplicationConfig> {
EventPubSub.start(); EventPubSub.start();
// Register Event publishers // Register Event publishers
registerEventPublisher(catalogConfig); registerEventPublisher(catalogConfig);
// start authorizer after event publishers
// authorizer creates admin/bot users, ES publisher should start before to index users created by authorizer
authorizer.init(catalogConfig.getAuthorizerConfiguration(), jdbi);
} }
@SneakyThrows @SneakyThrows