Configuring a Custom SAML App for JumpCloud SSO with Mabl
We recently added Mabl to our suite of Engineering Tools and wanted to get it configured to work with JumpCloud SSO. The Mabl support team we were working with did not have experience in using JumpCloud as an SSO provider so the best they could do was offer us their instructions for setting it up with Okta and then we went through a series of trial/failure troubleshooting steps until we found the configuration that worked successfully. I wanted to create this quick guide in case anyone else is faced with this scenario so that you will have a more seamless experience in getting it set up the first time.
When setting this up, you will need to reach out to Mabl Support or your Mabl CSM and they will provide you with the following information which will roughly look like this (actual URLs will be specific to your account):
In JumpCloud SAML 2.0 terminology these values are mapped accordingly:
You now have the necessary info to create the SAML 2.0 Custom Connector within JumpCloud. When doing so, here is all the information that you will need.
Save the connection and then download/export the metadata XML file as you will need to provide this to Mabl support so that they can finish the configuration on their side of things. If necessary, you should create the appropriate JumpCloud User Group that this SSO Connector will be bound to or, if appropriate, bind it to an existing group. I would suggest not adding any users at this point as you will want to test and verify the connection before performing a full rollout. Once you are ready, send the exported SSO metadata file to Mabl support so they can finish setup on their side of things.
It is likely they will have also asked if you would like any domains to be locked to your account for SSO purposes. Obviously, do what makes sense for your organization, but it is likely that you will want your primary domain to be locked so that it forces the use of SSO. If this is desired, provide the appropriate domain name(s) to them.
Once Mabl support has everything set up on their end they will let you know and ask that you test the connection. Add a test user to the previously created or designated JumpCloud User Group and then have that user attempt to launch Mabl from the JumpCloud User Console.
If successful, it will do one of the following:
If unsuccessful, you will likely get an error indicating that the connection was unsuccessful. Should this happen, you will need to work with Mabl support to troubleshoot.
Once you have confirmed that it is working, you should be all set for existing Mabl users. If this is a new installation or when providing access to new employees you will need to add them to the JumpCloud User Group that is bound to the Mabl SSO connector and also invite them to your workspace within Mabl.
For reference, here are our working connection settings: