mc idp ldap add
Description
The mc idp ldap add command creates an AD/LDAP IDP server configuration.
MinIO supports no more than one (1) AD/LDAP provider per deployment.
The following example sets the AD/LDAP configuration settings for the myminio deployment.
mc idp ldap add \
myminio \
server_addr=myldapserver:636 \
lookup_bind_dn=cn=admin,dc=min,dc=io \
lookup_bind_password=somesecret \
user_dn_search_base_dn=dc=min,dc=io \
user_dn_search_filter="(uid=%s)" \
group_search_base_dn=ou=swengg,dc=min,dc=io \
group_search_filter="(&(objectclass=groupofnames)(member=%d))"
The command has the following syntax:
mc [GLOBALFLAGS] idp ldap add \
ALIAS \
[CFG_PARAM1] \
[CFG_PARAM2]...
Replace
ALIASwith the alias of a MinIO deployment to create for AD/LDAP integration.Replace the
[CFG_PARAM#]with each of the configuration setting key-value pairs in the format ofPARAMETER="value".
Brackets
[]indicate optional parameters.Parameters sharing a line are mutually dependent.
Parameters separated using the pipe
|operator are mutually exclusive.
Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.
Parameters
- ALIAS
- Required
The alias of the MinIO deployment on which to add an AD/LDAP integration.
For example:
mc idp ldap add myminio \ server_addr=myldapserver:636 \ lookup_bind_dn=cn=admin,dc=min,dc=io \ lookup_bind_password=somesecret \ user_dn_search_base_dn=dc=min,dc=io \ user_dn_search_filter="(uid=%s)" \
- server_addr
- Required
Specify the hostname for the Active Directory / LDAP server. For example:
ldapserver.com:636
srv_record_nameautomatically identifies the portIf your AD/LDAP server uses
DNS SRV Records, do not append the port number to yourserver_addrvalue. SRV requests automatically include port numbers when returning the list of available servers.This parameter corresponds with the
MINIO_IDENTITY_LDAP_SERVER_ADDRenvironment variable.
- lookup_bind_dn
- Required
Specify the Distinguished Name (DN) for an AD/LDAP account MinIO uses when querying the AD/LDAP server. Enables Lookup-Bind authentication to the AD/LDAP server.
The DN account should be a read-only access keys with sufficient privileges to support querying performing user and group lookups.
This parameter corresponds with the
MINIO_IDENTITY_LDAP_LOOKUP_BIND_DNenvironment variable.
- lookup_bind_password
- Required
Specify the password for the Lookup-Bind user account.
Changed in version RELEASE.2023-06-23T20-26-00Z: MinIO redacts this value when returned as part of
mc admin config get.This parameter corresponds with the
MINIO_IDENTITY_LDAP_LOOKUP_BIND_PASSWORDenvironment variable.
- user_dn_attributes
- Optional
New in version RELEASE.2024-06-06T09-36-42Z.
Comma-separated list of user DN attributes.
Some valid values include,
uid,cn,mail,sshPublicKey.To enable public authentication for LDAP users, pass
sshPublicKeyas a DN attribute. The user can then use the passed SSH Public Key to log in to SFTP servers.mc idp ldap update ALIAS user_dn_attributes=sshPublicKey
- user_dn_search_base_dn
- Required
Specify the base Distinguished Name (DN) MinIO uses when querying for user credentials matching those provided by an authenticating client.
Separate multiple DNs with a semicolon (
;).For example:
cn=miniousers,dc=myldapserver,dc=net;ou=swengg,dc=min,dc=io
Supports Lookup-Bind mode.
This parameter corresponds with the
MINIO_IDENTITY_LDAP_USER_DN_SEARCH_BASE_DNenvironment variable.
- user_dn_search_filter
- Required
Specify the AD/LDAP search filter MinIO uses when querying for user credentials matching those provided by an authenticating client.
Use the
%ssubstitution character to insert the client-specified username into the search string. For example:(userPrincipalName=%s)
This parameter corresponds with the
MINIO_IDENTITY_LDAP_USER_DN_SEARCH_FILTERenvironment variable.
- comment
- Optional
Specify a comment to associate to the AD/LDAP configuration.
This parameter corresponds with the
MINIO_IDENTITY_LDAP_COMMENTenvironment variable.
- enabled
- Optional
Set to
falseto disable the AD/LDAP configuration.If
false, applications cannot generate STS credentials or otherwise authenticate to MinIO using the configured provider.Defaults to
trueor “enabled”.
- group_search_base_dn
- Optional
Specify a semicolon-separated (
;) list of group search base Distinguished Names MinIO uses when performing group lookups.For example:
cn=miniogroups,dc=myldapserver,dc=net;ou=swengg,dc=min,dc=io
This parameter corresponds with the
MINIO_IDENTITY_LDAP_GROUP_SEARCH_BASE_DNenvironment variable.
- group_search_filter
- Optional
Specify an AD/LDAP search filter for performing group lookups for the authenticated user
Use the
%ssubstitution character to insert the client-specified username into the search string. Use the%dsubstitution character to insert the Distinguished Name of the client-specified username into the search string.For example:
(&(objectclass=groupOfNames)(memberUid=%s))
When providing an AD/LDAP group search filter, configure a filter that returns the minimum number of relevant groups for the purpose of supporting authentication. Filters that return large group assignments increase the size of associated calls and resources. Functions sensitive to large request or response bodies may exhibit unexpected behaviors as a result.
This parameter corresponds with the
MINIO_IDENTITY_LDAP_GROUP_SEARCH_FILTERenvironment variable.
- server_insecure
- Optional
Specify
onto allow unsecured (non-TLS encrypted) connections to the AD/LDAP server.MinIO sends AD/LDAP user credentials in plain text to the AD/LDAP server, such that enabling TLS is required to prevent reading credentials over the wire. Using this option presents a security risk where any user with access to network traffic can observe the unencrypted plaintext credentials.
Defaults to
off.This parameter corresponds with the
MINIO_IDENTITY_LDAP_SERVER_INSECUREenvironment variable.
- server_starttls
- Optional
Specify
onto enableStartTLSconnections to an AD/LDAP server.Defaults to
offFor more about
StartTLS, refer to section 4.14 of the LDAP RFC 4511 specification.This parameter corresponds with the
MINIO_IDENTITY_LDAP_SERVER_STARTTLSenvironment variable.
- srv_record_name
- Optional
New in version RELEASE.2022-12-12T19-27-27Z.
Specify the appropriate value to enable MinIO to select an AD/LDAP server using a DNS SRV record request.
When enabled, MinIO selects an AD/LDAP server by:
Constructing the target SRV record name following standard naming conventions.
Requesting a list of available AD/LDAP servers.
Choosing an appropriate target based on priority and weight.
The configuration examples below presume the AD/LDAP server address is set to
example.comand the SRV record protocol is_tcp.For SRV record names beginning with
_ldap, specifyldap. The constructed DNS SRV record name resembles the following:_ldap._tcp.example.com
For SRV record names with beginning with
_ldaps, specifyldaps. The constructed DNS SRV record name resembles the following:_ldaps._tcp.example.com
If your DNS SRV record name uses alternate service or protocol names, specify
onand provide the full record name as your LDAP server address. Example:_ldapserver._specialtcp.example.comFor more about DNS SRV records, see DNS SRV Records for LDAP.
Server address for DNS SRV record configurations
The specified server name must not include a port number. This is different from a standard AD/LDAP configuration, where the port number is required.
See
server_addrorMINIO_IDENTITY_LDAP_SERVER_ADDRfor more about configuring an AD/LDAP server address.This parameter corresponds with the
MINIO_IDENTITY_LDAP_SRV_RECORD_NAMEenvironment variable.
- tls_skip_verify
- Optional
Specify
onto trust the AD/LDAP server TLS certificates without verification. This option may be required if the AD/LDAP server TLS certificates are signed by an untrusted Certificate Authority (e.g. self-signed).Defaults to
offThis parameter corresponds with the
MINIO_IDENTITY_LDAP_TLS_SKIP_VERIFYenvironment variable.
Global Flags
This command supports any of the global flags.
Behavior
S3 Compatibility
The mc commandline tool is built for compatibility with the AWS S3 API and is tested with MinIO and AWS S3 for expected functionality and behavior.
MinIO provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported. While mc commands may work as documented, any such usage is at your own risk.