Administrators with MTP admin keys could not identify users to bind in previous versions of the ADMU if they were using their MTP API Key. This release addresses this limitation by specifically prompting admins to select a MTP Org if a MTP Key is detected.
Is there anything particularly tricky?
Yes, many functions were changed in this module update. A MTP key is required to test this functionality.
How should this be tested?
The GUI App must be validated manually, test cases are written for the command line version of the tool
[Test Case: GUI Migration (MTP)]
With a Windows VM not bound to any tenant
Install JumpCloud on the VM and add to an MTP tenant
Run the JumpCloud GUI from this branch
Select AutoBindJC user and add an MTP API Key
Select an Org
type a user to perform a username search
migrate a user with the autobind JC username box checked
The user should be matched with a user in the MTP tenant, migrated and bound to the device after ADMU
[Test Case: CLI Migration (MTP)]
With a Windows VM not bound to any tenant
locally import "Start-Migration.ps1"
Run the ADMU command line version on a AD user ex:
The agent should be installed, the user should be matched with a user in the MTP tenant, migrated and bound to the device after ADMU
Screenshots
New GUI displays OrgName/ OrgID after an API Key is validated:
When an MPT Key is validated a GUI prompt is presented, admins can select one org from a dropdown list. Org IDs are presented because Org Names are not unique:
Changed behavior:
When the AutoBind JumpCloud User option is selected. A validation step now occurs and the API Key is checked before migration begins.
If the Key is an MTP Key and no Organization ID is provided, the script will error and exit
If the ORG ID is provided, the script will validate that the Key and ORG ID match. This behavior is the same for a non-MTP Admin key. As such there should be no need for Non-MTP admins to edit their scripts and pass in an ORG ID. MTP Admins will need to do this
Issues
What does this solve?
Administrators with MTP admin keys could not identify users to bind in previous versions of the ADMU if they were using their MTP API Key. This release addresses this limitation by specifically prompting admins to select a MTP Org if a MTP Key is detected.
Is there anything particularly tricky?
Yes, many functions were changed in this module update. A MTP key is required to test this functionality.
How should this be tested?
The GUI App must be validated manually, test cases are written for the command line version of the tool
[Test Case: GUI Migration (MTP)]
[Test Case: CLI Migration (MTP)]
Start-Migration -JumpCloudUserName "james.lowery" -SelectedUserName "S-1-12-1-64447351-1339341875-2832918416-977843340" -TempPassword T#st123456789 -InstallJCAgent $true -JumpCloudConnectKey "MTP_Tenant_Connect_Key" -AutobindJCUser $true -JumpCloudAPIKey "MTP_API_KEY" -JumpCloudOrgID "MTP_ORG_ID"Screenshots
New GUI displays OrgName/ OrgID after an API Key is validated:
When an MPT Key is validated a GUI prompt is presented, admins can select one org from a dropdown list. Org IDs are presented because Org Names are not unique:
Changed behavior: When the AutoBind JumpCloud User option is selected. A validation step now occurs and the API Key is checked before migration begins.
If the Key is an MTP Key and no Organization ID is provided, the script will error and exit
If the ORG ID is provided, the script will validate that the Key and ORG ID match. This behavior is the same for a non-MTP Admin key. As such there should be no need for Non-MTP admins to edit their scripts and pass in an ORG ID. MTP Admins will need to do this