Hi Yufei,

You bring up a good point.

Adding a secure way to manage credentials would certainly help Polaris
administrators.

I think this feature is related to the old secrets manager discussion
[1][2]. Perhaps it is time to revive it. IIRC, Polaris has only an
in-memory implementation now.

Current Quarkus configuration-based secrets certainly do look inconvenient
in a multi-organisation deployment. However, they still offer a reasonable
degree of security in cases where a single organisations controls all
realms and catalogs. From my POV the key aspect is that current
configuration can be connected to k8s secrets, managed by the deployment
administrators.

Managing secrets inside Polaris, requires a more diligent approach; hence,
my proposal to reopen the discussion about a more general Secrets Manager,
which can certainly be reused for holding storage credentials too.

Cheers,
Dmitri.

[1] https://lists.apache.org/thread/2y2vv8jrgps7s3sr241k6tgm440jzbp9
[2] https://lists.apache.org/thread/slpvcqzvcg0by5o7kwx36l6rkho2351o


On Fri, Nov 13, 2026 at 7:01 PM Yufei Gu <[email protected]> wrote:

> Hi everyone,
>
> While reviewing PR 5664, (https://github.com/apache/polaris/pull/5664) I
> found storageName requires the admin creating a connection to know a name
> configured on the server. That is awkward when catalog admins and Polaris
> deployment admins are different people. It’s very likely in a multi-realm
> Polaris deployment.
>
> Polaris already uses this pattern for storage credentials (#3409 (
> https://github.com/apache/polaris/pull/3409)). I think we can keep it and
> improve discovery.
>
> One idea is to treat these names as credential profiles and later let users
> list the profiles they are allowed to use. They would select one and put
> its name into storageName. Credentials would stay on the server, and
> existing configurations would continue to work.
>
> This would let catalog admins choose credentials without inspecting server
> configuration or asking deployment admins for each name. Both listing and
> using a profile should respect permissions.
>
> WDYT?
>
> Thanks,
> Yufei
>

Reply via email to