snazy commented on PR #461:
URL: https://github.com/apache/polaris/pull/461#issuecomment-2531300792

   I'm quite open (and probably brutal) here: logging or storing plain/clear 
text credentials is a severe security issue that justifies a CVE. The process 
of creating credentials must really be a command that only allows the user to 
grab the secrets - but only once - not stored anywhere - not explicitly or 
implicitly (or ephemerally), accessible by other tools (database, logging 
system/files, etc). If the user does not grab the generated secrets, bummer. If 
the bootstrap process cannot ensure this, then the bootstrap process _has_ to 
be changed. Security is a very sensitive topic - and and absolute necessity for 
the production readiness of Apache Polaris!
   
   Generally, I do not think that Apache Polaris should get into the business 
of handling identities or secrets, but rather interface w/ systems that are 
purely there for these kinds of things. The currently built-in secrets handling 
should IMHO entirely go away.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to