Druid-basic-security

Hi Chris,

Did you define the Escalators, e.g:

# Escalator
druid.escalator.type=basic
druid.escalator.internalClientUsername=druid_system
druid.escalator.internalClientPassword=password2
druid.escalator.authorizerName=MyBasicAuthorizer

http://druid.io/docs/latest/development/extensions-core/druid-basic-security.html

Ming

Hi Ming. I actually configured the escalators and got the same errors. At this point I have them commented out. Are they a requirement from the beginning?

As i said…coordinator starts…but the overlord on the same node will not start. Do u recommend
druid.auth.basic.common.cacheDirectory?

I actually configured the escalators and got the same errors. At this point I have them commented out. Are they a requirement from the beginning?

What was the config you had for the escalator? They are necessary from the beginning (they control how the Druid processes authenticate when communicating with other Druid processes).

You could try verifying if the credentials used by the escalator are working by accessing the /status endpoint on the coordinator, e.g:

curl -u user:pass http://localhost:8081/status

Thank you Jonathan.

I used the same configuration in the example from the druid-basic-security page. All i did was provide a different password. I will add it back and ceck the status endpoint when i am in the office tomorrow.

Thanks so much.

Yes, please also make sure the config
"druid.escalator.internalClientUsername=druid_system

druid.escalator.internalClientPassword=Client123!"

which shall be the same as “druid.auth.authenticator.MyBasicAuthenticator.initialInternalClientPassword” , because you cannot have two passwords for a same “druid_system” user. Otherwise, you will see coordinator starts up fine, but overlord runs into the errors you described.

Ming