nsscache retrieves user, group, shadow, and SSH key data from a SCIM source, along with the optional LDAP parameters SUNK adds to upstream nsscache. Use it when tuning identity sync behavior for a SUNK cluster.
Available parameters for SCIM
SCIM source options
The following options configure the behavior of the SCIM source:SCIM source options
SCIM source options
SCIM path configuration options
The following path configuration options let you customize how data is extracted from SCIM responses. These can be set per-map in[passwd], [group], [shadow], and [sshkey] sections.
SCIM path configuration options
SCIM path configuration options
[shadow] map parameters for SCIM
The shadow map creates shadow(5) format entries for user data from the SCIM users endpoint. This requires only the scim_path_username configuration in the [shadow] section, because other shadow fields are generally not available from SCIM sources. All shadow entries are created in the format username:*:::::::, where * indicates that authentication is handled elsewhere (not through local password files).
The following optional configuration parameters are available for the [shadow] section to provide default values for shadow fields:
SCIM shadow parameters
SCIM shadow parameters
Optional parameters for LDAP
SUNK adds optional parameters tonsscache for LDAP.
Default shell
Thensscache.nsscacheConfig.default.ldap_default_shell parameter provides a default shell for all users. You can specify a different shell with the loginShell value in the user attributes configuration.
This parameter differs from the ldap_override_shell, which sets a shell that overrides the user’s preferences in their LDAP profile.
Home directory override
Use thensscache.nsscacheConfig.default.ldap_override_home_dir parameter for a home directory override. Use %%u to substitute the username in the home directory.
Use this to set a mount point for the home directories. For example, /mnt/home/%%u. The mount point should match the mount specified in compute.VolumeMounts.