Browse Source
shell: fix s3.configure to use credential manager when configured
shell: fix s3.configure to use credential manager when configured
Fixes #8025 This commit resolves the user management inconsistency between the Admin UI and the s3.configure command when using a credential backend (e.g., PostgreSQL). Previously: - Admin UI used credentialManager to read/write users from the configured backend - s3.configure always wrote directly to filer at /etc/iam/identity.json - This caused users created via Admin UI to not appear in listings, and users created via s3.configure to not persist to the credential backend Changes: - s3.configure now detects if a credential backend is configured via credential.toml - When a backend is detected, it uses credentialManager to load and save configuration - Falls back to filer-based storage when no backend is configured (backward compatible) This ensures both Admin UI and s3.configure use the same storage backend, resolving the inconsistency.fix-s3-configure-consistency
1 changed files with 68 additions and 17 deletions
Write
Preview
Loading…
Cancel
Save
Reference in new issue