[GitHub] [druid] jihoonson commented on issue #9351: Adding CredentialProvider, deprecating PasswordProvider

[GitBox <gi...@apache.org>]

jihoonson commented on issue #9351: Adding CredentialProvider, deprecating PasswordProvider
URL: https://github.com/apache/druid/issues/9351#issuecomment-584812032
 
 
   @maytasm3 thank you for taking a look.
   
   > * Do we need to deprecate PasswordProvider? Can we have both? The reason is that there might be no username and just a password or a single field that needs to be secured. i.e. things that are keys (access key, API keys, etc.)
   
   I think the use cases of `PasswordProvider` and `CredentialProvider` are pretty overlapped. Would you elaborate more on the example applications that require a password but not an account we should consider?
   
   > * What if Druid user wants to secured username and password differently? Is this still possible? For example, a user might pass username as plaintext and password with environment variable
   
   I think this would be pretty rare, but it's still possible with a custom credential provider.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org