docs/doc/source/security/kubernetes/sssd-support-5fb6c4b0320b.rst

SSH User Authentication using Windows Active Directory (WAD)

By default, to hosts supports authentication using the 'sysadmin' Local Linux Account and Local Linux User Accounts. can also be optionally configured to support authentication with 1 or more remote identity providers (such as ). Internally, uses service to provide NSS and PAM interfaces and a backend system able to remotely connect to multiple different domains.

provides a secure solution by using data encryption for user authentication. supports authentication only over an encrypted channel.

In summary the / solution for remote authentication includes:

• Multi domain remote authentication
• Extra security by using data encryption for user authentication
• Offline authentication if a identity store is unavailable, by caching users and managing caching timeout and refresh
• High authentication and authorization performance

In a maximum of 3 domains are supported besides the local Openldap domain.

Note

SSH/SSSD authentication configuration described in this section also applies to local console logins.

You can find more information about configuration at https://linux.die.net/man/5/sssd.conf and https://linux.die.net/man/5/sssd-ldap.

Install WAD CA Certificate

To be able to successfully connect to a domain through a secure connection, requires the Certificate of the that signed the remote server's SSL Certificate to be installed on the system. The certificate needs to be installed before the corresponding AD domain is added.

The command to add certificate:

system ca-certificate-install <AD CA certificate file>

Add Remote WAD Domain

A maximum of three remote AD domains are supported in : ldap-domain1, ldap-domain2, ldap-domain3. Each domain needs to be configured using mandatory and optional service parameters. Each parameter will be validated according to industry standard validation rules for correct syntax that apply to domain names, ldap url, and directory names. An error message will be displayed if the parameter does not have the standard syntax.

Mandatory parameters

To add a new remote ldap domain the following mandatory parameters need to be added using system service parameter commands:

• domain_name

  A valid domain name (example: wad.mydomain.com) that will be the name of the domain configuration section (example: [domain/<domain name>]).

• ldap_uri

  The server URI that the client needs to connect to. For example: ldaps://wad.mydomain.com where ldaps indicates that the secure protocol should be used for the connection. This attribute can accept the IP address of the server but it is not recommended.

• ldap_access_filter

  An search filter criteria that must be met for the user to get access on this host. All the server supported filters are allowed. For the supported filters, see https://learn.microsoft.com/en-us/archive/technet-wiki/5392.active-directory-ldap-syntax-filters. Verify that the filter is valid using the ldapsearch command prior to setting it in the ldap_access_filter parameter.

  Note

  Offline caching for this feature is limited to determining whether the user's last online login was granted access permission. If they were granted access during their last login, they will continue to get access while offline and vice-versa.

• ldap_search_base

  The default base used to perform searches. The filter must be a valid search filter as specified by http://www.ietf.org/rfc/rfc2254.txt. Example: ldap_search_base=CN=Users,DC=wad,DC=mydomain,DC=com.

• ldap_default_bind_dn

  The default bind used to perform operations. Example: ldap_default_bind_dn=CN=Administrator,CN=Users,DC=wad,DC=mydomain,DC=com.

• ldap_default_authtok

  The authentication token of the default bind . Currently, only clear text passwords are supported.

If a mandatory parameter is missing, an error will be displayed, naming the missing parameter for the domain and the domain will not be created.

Commands to add mandatory parameters for a remote ldap domain:

system service-parameter-add <service_name> <section_name> parameter_name=<parameter_value>

# <service_name> is “identity” for all domains.
# <section_name> identifies a domain as either “ldap-domain1”, “ldap-domain2” or “ldap-domain3”.

Example:

system service-parameter-add identity ldap-domain1 domain_name=ad.wad-server.com

system service-parameter-add identity ldap-domain1 ldap_uri=ldaps://ad.wad-server.com

system service-parameter-add identity ldap-domain1 ldap_access_filter=memberOf=CN=allowedusers,CN=Users,DC=wad-server,DC=com

system service-parameter-add identity ldap-domain1 ldap_search_base=CN=Users,DC=wad-server,DC=com

system service-parameter-add identity ldap-domain1 ldap_default_bind_dn=CN=Administrator,CN=Users,DC=wad-server,DC=com

system service-parameter-add identity ldap-domain1 ldap_default_authtok =Passw0rd*

Note

The ldap_access_filter service parameter can be configured to allow access to the Linux host. In the following example, the access is restricted to members of the group allowedusers. Users that are not part of allowedusers will get the message authentication failed. Here, allowedusers is an example of a group.

system service-parameter-add identity ldap-domain1 ldap_access_filter=memberOf=CN=allowedusers,CN=Users,DC=wad-server,DC=com

The allowedusers group is a group where the gidNumber attribute must be set to a unique group number among Linux groups so that it is mapped on the Linux platform as a Linux group with a unique gid value.

For more details on parameters, refer to https://linux.die.net/man/5/sssd-ldap.

Optional Parameters

There are two optional domain parameters that can be added using system service parameter commands:

• ldap_user_search_base

  An optional base , search scope, and filter to restrict searches for user objects. If not specified, the default value is ldap_search_base.

• ldap_group_search_base

  An optional base , search scope, and filter to restrict searches for group objects. If not specified, the default value is ldap_search_base.

For example:

system service-parameter-add identity ldap-domain1 ldap_user_search_base=CN=Users,DC=wad-server,DC=com

system service-parameter-add identity ldap-domain1 ldap_group_search_base=CN=Groups,DC=wad-server,DC=com

For more details on parameters, refer to https://linux.die.net/man/5/sssd-ldap.

Apply parameters

After all the domain mandatory parameters are added and if needed, the optional ones, the parameters will be applied using service-parameter-apply command. Only after “apply” command the sssd domain configuration will be added to /etc/sssd/sssd.conf and becomes active, and the SSSD daemon will connect to the remote server.

The system service-parameter-apply command has been enhanced for this feature to include a section parameter that did not exist in the previous release. The new section parameter is an optional parameter of the service-parameter-apply command. In the context of the identity service ldap domains it is needed to specify the domain section name, as follows:

system service-parameter-apply <service-name> --section <section-name>

E.g.:

system service-parameter-apply identity --section ldap-domain1

Default WAD Domain Configuration

The default domain configuration parameters are pre-configured. Main default configuration settings include:

• Offline authentication is enabled, allowing users to still authenticate even if the ldap identity provider is unavailable. using their cached credentials. User credentials caching is enabled by parameter setting cache_credentials = true. After a successful login user credentials are stored as part of the user account in the cache.
• Domain enumeration is disabled by using the default setting enumerate = false for performance reasons.
• User home directory on the platform gets created after the first user login with the following path /home/<domain_name>/<user_name>.
• server certificate verification is always required by using the default setting for ldap_tls_reqcert parameter as demand.

SSH using the WAD domain user

Verify SSSD is Connected to the Domain

If the is connected to a domain, then the domain users have been discovered and cached on the host. The same applies to the domain groups.

Run getent passwd <user_login_name>@<domain_name>, to see if the user has been cached on the host.

getent passwd pvtest1@ad.wad-server.com

Run getent group <group_name>@<domain_name> to see the group and its members.

getent passwd eng@ad.wad-server.com

Remote SSH

Once the is connected to the domain, a domain user can be used to to the host. If a user has the same user login name in multiple domains, the domain name can be used to distinguish between the common name users.

ssh -l <domain_user_name>@<domain_name> <host_IP_address>

The automatically created home directory for the user is /home/<domain_name>/<user_name>.

Modify/Delete WAD Domain parameters

Modify an parameter for an ldap domain using system service parameter command.

The service-parameter-apply needs to follow the service-parameter-modify so the parameter value change can take effect.

For example:

system service-parameter-modify identity ldap-domain1 ldap_group_search_base=CN=Users,DC=wad-server,DC=com

system service-parameter-apply identity --section ldap-domain1

Regarding deleting domain parameters, only optional service parameters can be individually deleted:

system service-parameter-delete <parameter-uuid>

system service-parameter-apply identity --section <domain_section_name>

Delete a WAD Domain configuration

Optional domain parameters can be deleted individually.

Mandatory parameters cannot be deleted individually, is all or none.

To fully delete a domain, delete all the mandatory parameters and the configured optional parameters. After that, execute the service-parameter-apply` command.

system service-parameter-delete <parameter-uuid>

------------ delete all parameters of the domain-----------

system service-parameter-apply identity --section <domain_section_name>

Deleting a domain will cause the users to not show up with getent passwd command anymore even if they may have not been removed from cache just yet. The users will be removed from cache according to cache expiration configuration. The cache expiry configuration for this release, uses default values.

The users home directories created on the platform will not be removed after the domain configuration is removed. It is administrator's responsibility to clean up users' home directories that are no longer used.

Default Local OpenLDAP Domain Configuration

The configuration for the local OpenLDAP domain is part of the default configuration.

All the local OpenLDAP domain parameters are pre-configured. Main default configuration settings include:

• Domain enumeration is enabled as the local domain number of users is not as large to pose performance issues. The use of command getent passwd will list all the remote domain discovered users.
• The user home directory on the platform gets created after the first user login and has the following path /home/<user_name>.
• server certificate verification is always required by using the default setting for ldap_tls_reqcert parameter as demand.

The OpenLDAP certificate is created and managed internally by platform.

SSSD logs

logs can be viewed on the host, in directory /var/log/sssd/sssd.log. Each domain also has its own log file: /var/log/sssd/sssd_<domain_name>.log.