Configuration
Once the RapidIdentity Client for Windows file is installed follow these steps to edit the configuration file.
Locate Server.configuration in Identity Automation > Rapid Identity Client for Windows
Copy the Server file to the computer’s desktop and open it to enter the following edits:
Under the section titled “[/Workstation]” enter the following after DefaultDomain=:
For nondomain machines: add a period (.)
Note
Example: DefaultDomain=.
This authenticates with the user that the credentials provided will allow access to the local machine only.
Important
This computer must have a user account set up to proceed, in order for it to be used as a local machine.
Additionally, the RapidIdentity User account password must match the password for the local user account that is created.
Ideally, the passwords would be set to never expire on both the local machine, and on the RapidIdentity server when using local accounts for non-domain joined workstations.
For domain-joined machines: enter the name of the domain, which is the NetBIOS name.
Note
Example: DefaultDomain=(insert NetBIOS name)
Save changes.
Move the edited Server file back into its original directory (Identity Automation > RapidIdentity Client for Windows).
Click to Replace the file in the destination and press Continue to provide administrator permission to copy the file to the RapidIdentity Client for Windows folder.
Once the file is edited, a reboot can be performed at this time, but it is not necessary.
Connecting to Non-Domain-Joined Computers
If using a non-domain joined computer you will need to ensure that both passwords are the same. RapidIdentity is connected to a domain to manage user accounts. The password that is stored in the RapidIdentity domain must match the local account password when using non-domain joined computers so that Windows is able to establish a session when the user account information is presented to the system.
Connecting to Domain-Joined Computers
If using a domain joined computer, ensure that the RapidIdentity server is configured to use the same domain. Windows will then be able to establish a session using the RapidIdentity user account linked to Active Directory. Additionally, users will be able to reset their domain password through the RapidIdentity portal, if necessary.