Say I have a backup administrator and a delegated admin with a more restricted role.
They can define credentials which I am not allowed to see as backup admin for some reason. However, as an admin, I can see (and edit) their jobs if need be. But if I do, it will reset credentials to default (apparently default behavior since I cannot see those used in the first place).
Conversely, delegated user faces same challenge: If I create my own set of credentials and use it in what is actually their job (maybe just to get it working again), they will override it to default on their next edit, potentially not realizing this, and the job will again fail.
This is apparently "by design", however, at least, safer handling/warnings to prevent accidental breakage is required
E.g. not overwrite credentials if currently defined credentials are out of scope for the user currently editing.
(Case # 08122374)
-
jeronimo
- Influencer
- Posts: 15
- Liked: 2 times
- Joined: May 04, 2026 12:34 pm
- Contact:
-
HannesK
- Product Manager
- Posts: 16285
- Liked: 3723 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: RBAC credential visibility
Hello,
I cannot follow the steps... can you maybe describe step by step what the admin and the restricted user do? In general, nobody can see credentials (also not admin his own). They are always hidden and one can only verify for example encryption passwords by typing them in and click "verify".
Best regards
Hannes
I cannot follow the steps... can you maybe describe step by step what the admin and the restricted user do? In general, nobody can see credentials (also not admin his own). They are always hidden and one can only verify for example encryption passwords by typing them in and click "verify".
Best regards
Hannes
Who is online
Users browsing this forum: AdsBot [Google], EviLin and 203 guests