Open topic with navigation

# Automatic Logins/Tokenized Encrypted Passwords

Once upon a time, "automatic logins" would allow any user logging into the system to have access to the software and not require a login for every user. Today, this capability is achieved through tokenized encrypted passwords.

The following instructions will allow the system administrator to log in and generate a license token using that system's Maxon App mx1 tool. Once generated, a non-admin user may log into that system and utilize Maxon products available for the Maxon account with which the admin logged in.

To store the password, the admin will need to open the mx1 tool using the Command Prompt in Administrator mode on Windows or Terminal on Mac.

### Mac:

1. Launch Terminal

2. cd to the Maxon App Tools folder

cd /Library/Application\ Support/Maxon/Tools

### Windows:

1. Open Command Prompt (in admin mode)

2. cd to the Maxon App Tools folder

cd C:\Program Files\Maxon\Tools

From here you will need to enter the mx1 command below. For best results, ensure that you enclose both the [username] and [password] in quotes. For Mac use a single quote and for Windows use a double quote.

### Mac:

./mx1 user login -u '[username]' -p '[password]' --store

### Windows:

mx1 user login -u "[username]" -p "[password]" --store

For example if your username is blanston.gern@wacg.com with a password of Cru3lSh03s! and you want to use the Terminal on Mac, the resulting command would be:

./mx1 user login -u 'blanston.gern@wacg.com' -p 'Cru3lSh03s!' --store

If successful, the "Successfully logged in" message will appear. If you wish to view the token, include the flag -v in the above command.

You can also omit the -p [password] from the command. This requires the admin to enter the password manually immediately following the press of the Enter key. The command line does not show the password as it is being typed. However, you will know the password is incorrect if you receive a login error.

Optionally, the admin can use the mx1 user info command to confirm that the user correctly logged in. Otherwise, the admin may now log out of the OS. From here, a non-admin account can log into the machine. The license token is stored and product use becomes available. There is no need to open the Maxon App GUI.

Logging out of the account removes the hashed token. This needs to be done via the mx1 tool with the mx1 user logout command. Once in stored password token mode, the option to logout via the Maxon App GUI is removed until the user removes the token.

If you wish to keep the non-admin user from having access to the Maxon App GUI (which allows them to assign/release licenses, install/uninstall programs, etc.), you can move the Maxon App GUI to the admin account's desktop. This allows the admin to access the Maxon App GUI's features, such as those mentioned above, as well as doing things like creating a bug report for troubleshooting any issues. You can find the Maxon App GUI executables in the location below.

### Mac:

/Applications/Maxon App

### Windows:

C:\Program Files\Maxon\App Manager\Maxon App.exe

You can also install a headless version of the Red Giant Service that includes all essential items. Only the GUI will be absent if the admin does not wish non-admin accounts to have an interface with which to interact. Instructions for this can be found on this guide's Scripted Installs page.