What is the recommend way to authenticate with Apache Pulsar in a multi-user production environment? #352
|
I have an Apache Pulsar instance configured with JWT authentication. Setting DEKAF_DEFAULT_PULSAR_AUTH works, but is a security risk (as said in the configuration reference. How do I configure Dekaf so users provide their own credentials/tokens in the Dekaf UI? When not setting DEKAF_DEFAULT_PULSAR_AUTH I get a popup, which you can't get rid of, stating 'There are connectivity issues'. If I remove it through devtools I can provide credentials and everything works. Is my configuration wrong or is this a bug in the UI? |
Replies: 1 comment
|
@ptemarvelde hi, It's a UI bug and it been already reported a few months ago, but I didn't have time for it and forgot. I created a ticket for this: #353 Overall the whole auth/authz system worth revisiting. It's been planned for long time and I have implementation draft for it on a local branch. |
@ptemarvelde hi,
Thank you for raising this.
It's a UI bug and it been already reported a few months ago, but I didn't have time for it and forgot.
The popup should be closable and provide useful information about missing auth and how user can fix it by adding credentials on UI.
I created a ticket for this: #353
I'll try to take care on it at this week. For now, devtools hack is the way.
Overall the whole auth/authz system worth revisiting. It's been planned for long time and I have implementation draft for it on a local branch.
The current simple auth system is planned to be keeped for the backward compatibility.