mirror of
https://github.com/minio/docs.git
synced 2025-08-09 13:02:53 +03:00
Correct mc admin user example, fix warnings (#969)
A few small things: * find/replace error from https://github.com/minio/docs/pull/950 * build warnings Thank you @bendem! https://github.com/minio/docs/pull/950#discussion_r1303044374
This commit is contained in:
@@ -117,7 +117,7 @@ MinIO uses :ref:`Policy Based Access Control (PBAC) <minio-access-management>` t
|
||||
When using an Active Directory/LDAP server for identity management (authentication), MinIO maintains control over access (authorization) through PBAC.
|
||||
|
||||
When a user successfully authenticates to MinIO using their AD/LDAP credentials, MinIO searches for all :ref:`policies <minio-policy>` which are explicitly associated to that user's Distinguished Name (DN).
|
||||
Specifically, the policy must be assigned to a user with a matching DN using the :mc-cmd:`mc idp ldap policy attach` command.
|
||||
Specifically, the policy must be assigned to a user with a matching DN using the :mc:`mc idp ldap policy attach` command.
|
||||
|
||||
MinIO also supports querying for the user's AD/LDAP group membership.
|
||||
MinIO attempts to match existing policies to the DN for each of the user's groups.
|
||||
|
@@ -279,7 +279,7 @@ Disable a Configured Active Directory / LDAP Connection
|
||||
|
||||
You can enable and disable the configured AD/LDAP connection as needed.
|
||||
|
||||
Use :mc-cmd:`mc idp ldap disable` to deactivate a configured connection.
|
||||
Use :mc-cmd:`mc idp ldap enable` to activate a previously configured connection.
|
||||
Use :mc:`mc idp ldap disable` to deactivate a configured connection.
|
||||
Use :mc:`mc idp ldap enable` to activate a previously configured connection.
|
||||
|
||||
You may also enable or disable AD/LDAP from the :ref:`MinIO Console <minio-console>`.
|
||||
|
@@ -171,7 +171,7 @@ Starting with :minio-release:`RELEASE.2023-05-27T05-56-19Z`, decommissioning ign
|
||||
This avoids creating empty metadata on the remaining server pool(s) for objects that are effectively fully deleted.
|
||||
|
||||
Starting with :minio-release:`RELEASE.2023-06-23T20-26-00Z`, decommissioning also ignores object versions which have expired based on the configured :ref:`lifecycle rules <minio-lifecycle-management-expiration>` for the parent bucket.
|
||||
Starting with :minio-release:`RELEASE.2023-06-29T05-12-28Z`, you can monitor ignored delete markers and expired objects during the decommission process with :mc:`mc admin trace --call decommission <mc admin trace --call>`.
|
||||
Starting with :minio-release:`RELEASE.2023-06-29T05-12-28Z`, you can monitor ignored delete markers and expired objects during the decommission process with :mc-cmd:`mc admin trace --call decommission <mc admin trace --call>`.
|
||||
|
||||
Once the decommissioning process completes, you can safely shut down that pool.
|
||||
Since the only remaining data was scheduled for deletion *or* was only a ``DeleteMarker``, you can safely clear or destroy those drives as per your internal procedures.
|
||||
|
Reference in New Issue
Block a user