This release removes the need for username lookup to be case sensitive when specifying the "AutoBind JumpCloud User" option of the ADMU GUI tool. In prior versions the specific casing was required.
In this example the "ITSupport" username will match any username in JumpCloud even if the JumpCloud username is described as an all lowercase string.
Is there anything particularly tricky?
How should this be tested?
Testing Case Sensitive Search
In a windows VM with an AD user Bound, Run the version of ADMU from this branch.
Take a snapshot to easily get back to this state
Attempt to migrate a user matching a "JumpCloud Username" in your test org. (Attempt this with an all uppercase string "ITSUPPORT" or lowercase "itsupport").
The JumpCloud API Key textbox & the "Autobind JC User" checkbox must be populated/ checked.
The user search should identify the JumpCloud user by username and the user should be bound to the device after migration.
This essentially involves creating a private github repository, creating a token with access to just that repository.
On the VM you've used to setup & test ADMU, run the Setup & Discovery Script. A .json file with the hostname for that system will be added to your github repository
On another system, Run the Investigation script to collate the results of all systems and upload a CSV to your github repository.
Edit the CSV directly in github (or locally and re-commit the file), for the user you wish to migrate, add a jumpcloud user in the "JumpCloudUserName" collumn. Save the file.
Lastly take a snapshot of your VM. Then run the remote invocation scrip from JumpCloud, scoped to your test VM. The specified user in the CSV should be migrated to the a JumpCloud username.
Screenshots
Discovery Script
Populated Collated CSV
Command invocation from JumpCloud, specified user was migrated:
Issues
What does this solve?
This release removes the need for username lookup to be case sensitive when specifying the "AutoBind JumpCloud User" option of the ADMU GUI tool. In prior versions the specific casing was required.
In this example the "ITSupport" username will match any username in JumpCloud even if the JumpCloud username is described as an all lowercase string.
Is there anything particularly tricky?
How should this be tested?
Testing Case Sensitive Search
Testing Advanced Deployment Scripts
Screenshots
Discovery Script
Populated Collated CSV
Command invocation from JumpCloud, specified user was migrated: