NoMAD Login

Defines the AD domain you're working with.

—

—

—

—

—

—

If set to yes, group membership lookups should be done recursively

If yes, migrate users

—

—

—

—

—

List of LDAP servers that you would like to use for AD authentication instead of using SRV record lookup.

—

Determines if NoMAD Login uses LDAP over SSL.

List of domains to append at the loginwindow. If not set, the standard Managed Domain policy will apply.

—

List of LDAP servers to display in the pulldown menu in the Login Window. Users can select a domain from the menu and then only enter the shortname in the text field.

—

Maps NT to AD Domains. e.g. NOMAD: nomad.menu, would allow a user to sign in as "NOMAD\user" and that would be converted to "user@nomad.menu" before authenticating to AD.

—

—

—

—

—

—

—

—

—

—

—

—

—

—

Text for the large title in the EULA window.

Text for a subtitle in the EULA window.

Text to present in the EULA window.

Path to save acceptance records to.

Will place any local user created at login by NoMAD Login in the local admin group.

List of groups that should have its members created as local administrators.

—

Use the the user's CN from AD instead of attempting to create the user name from the first and last name attributes of the user's AD record.

Uses the CN as the fullname on the account when the givenName and sn fields are blank

Path to an image to set as the user profile image.

Will convert a previously cached mobile account from AD into a regular local user account on login.

If true, the AltSecurityIdentities user record attribute should be preserved, useful when moving from mobile accounts with smart card mapping implemented.

If true, a password input at the NoMAD login window will be required to demobilize

Path where the userinfo.plist will be written.

Path to a logo file to use for the UserInput mechanism.

Title for the UserInput mechanism.

Text for the UserInput mechanism.

UI elements shown during the UserInput mechanism.

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

On systems using the APFS filesystem, this key will enable FileVault encryption as the user is signing in for the first time.

Write the output of the fdesetup command to /var/db/.NoMADFDESetup

—

—

If set to yes, a macOS-style loginscreen will be presented instead of the NoMAD Login loginwindow style.

Placeholder text to show in the username textfield.

Path to the logo to display on the login screen. If set to NONE, no logo will be shown.

Logo to display on the login screen.

Alpha value of the logo image.

Path to the background image to be used.

Background to display on the login screen.

Alpha value of the background image.

If enabled, the network selection button is shown

Defines which system information should be showed on login window, by default

If set to yes, hides the shutdown and restart buttons

This key will enable SecureToken management capabilites in NomadLogin 1.4. This utilizes a service account which can be modified from default using the below optional preferences.

If enabled, the SecureToken service account will only enable administrative users created with NoMAD Login.

—

If enabled, NoMAD Login will only enable the first user that is eligable for a SecureToken, and delete the service account afterwards.

—

—

—

Defines a custom SecureToken service account password length.

—

Message to show when the password needs to sync

—

—

—

String to determine the path of an executable that is run when a new user is created. It is expected to return the UID that the user should be created with. It passes in the new users username as the first argument, default is to use the built in functionality

String to determine the path of an executable that is run when a new user is created. It is expected to return the GUID that the user should be created with. It passes in the new users username as the first argument, default is to use the built in functionality

Adds the appropriate log file to the the Notify mechanism.

Create keychain if it does not exist.

Add a NoMAD entry into the keychain.

If defined it specifies the custom location of the application to be given access to the keychain item.

Shortname of the last user to login. This allows NoMAD to login on first launch.

Reset keychain if login password doesn't match.

Allows guest users login

List of names that can be entered into the username field to trigger a guest user creation

—

The path to write out the guest users randomly generated password

Defines the first name of the guest user account

Defines the last name of the guest user account

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—