[user.management.enable=false] - default user/password is not admin

[goncalocribeiro]

I've already seen the issue #347, which says it has been solved by #351 but that doesn't work. The default user/password continues to not be an admin user.

If I have my application.properties as follows:

If user.management.enable is true, the following account and password will no longer be valid.

pulsar-manager.account=pulsar pulsar-manager.password=pulsar

If true, the database is used for user management

user.management.enable=false

default environment configuration

default.environment.name=pulsar_local default.environment.service_url=http://xx.xx.xx.xx:8080

And then login with pulsar/pulsar, the default environment configuration is not even loaded. If I try to add a new environment, it says "User does not have permission to operate".

Please solve this issue. I believe that maybe, it needs to be added "headers.add("role", "admin");" in LoginController when user.management.enable=false.

Thanks

[gjanardh]

I am stuck with the above issue too. Any work arounds for this issue to use pulsar-manager 0.2.0?

[kponichtera]

I lost half a day trying to figure out why user.management.enable property doesn't work for me - the user specified by pulsar-manager.account didn't work for me at all. Turns out these properties are not used in the code anymore - the are just dead, autowired property values. The README also mentions:

If you are deploying Pulsar Manager 0.1.0 using the released container, you can log in the Pulsar Manager UI using the following credentials.

Account: pulsar Password: pulsar

If you are deploying Pulsar Manager using the latest code, you can create a super-user using the following command.

@goncalocribeiro The code in https://github.com/apache/pulsar-manager/pull/351 does not exist in the repository anymore. I'm wondering if making these properties dead was a deliberate change and sombody forgot to remove the dead code, or the functionality was lost as a result of some code cleanup. If it's the former case then it's a pity, cause it was very handy for the locally-deployed development Pulsar instances.