Need jump cloud IDP for SSO
Hi Team,
We require JumpCloud as the Identity Provider (IdP) for our Cerberus SSO setup, as we are currently migrating our identity management from Microsoft Entra ID to JumpCloud.
We would appreciate your support in enabling or adding JumpCloud IdP support for Cerberus SSO. If this is possible, please let us know the required steps or any available options to implement this.
Thanks
-
Official comment
Hi Dinesh,
Thank you for following up with us. We appreciate your patience. I will need to check with our engineering team on our Monday call for a status update. I will update this post as soon as I have additional information.
-
Hello Dinesh,
So we have a complete picture to send over to our product team, could you answer the following for us?
- What is the problem that this feature would fix?
- Why is it a problem?
- Is there a workaround you currently have for this problem?
- Do you have a suggestion on how you would like to see the problem fixed?
- How big is the problem? Who is affected by this problem (End Users, Admins, etc.)?
0 -
Below is the answers for your questions:
What is the problem that this feature would fix?
Our organization is migrating from Microsoft Entra ID to JumpCloud as our enterprise Identity Provider. Cerberus currently supports SSO integration with Microsoft Entra ID and Okta, but does not support JumpCloud as an IdP. Native JumpCloud SAML support would allow us to continue using SSO with Cerberus after our migration.
Why is it a problem?
Without JumpCloud support, we cannot authenticate users to Cerberus using our organization's standard identity platform. This prevents us from maintaining a centralized authentication process and requires us to either continue licensing Microsoft Entra ID solely for Cerberus or manage separate local accounts, increasing administrative overhead and security risk.
Is there a workaround you currently have for this problem?
There is no practical long-term workaround. Cerberus Support suggested using Okta for testing because it has a similar SAML implementation, but Okta is not our production Identity Provider. Maintaining Microsoft Entra ID exclusively for Cerberus is not a viable solution since our organization is migrating completely to JumpCloud.
Do you have a suggestion on how you would like to see the problem fixed?
We would like Cerberus to support JumpCloud as a SAML 2.0 Identity Provider. Ideally, Cerberus should allow administrators to configure JumpCloud using its standard SAML metadata (Metadata URL/XML), including support for:
- SAML 2.0 authentication
- Metadata import (URL or XML)
- User attribute mapping (NameID, Email, Groups)
- Single Logout (if supported)
This would provide compatibility with organizations using JumpCloud for identity management.
How big is the problem? Who is affected by this problem (End Users, Admins, etc.)?
This impacts both administrators and end users.
- Administrators are unable to integrate Cerberus with the organization's standard Identity Provider, resulting in additional account management and operational complexity.
- End users cannot use their corporate JumpCloud credentials to access Cerberus via Single Sign-On.
- As our organization transitions from Microsoft Entra ID to JumpCloud, this becomes a business-critical requirement to ensure uninterrupted and secure access to Cerberus without maintaining multiple identity platforms.
0 -
Hi Dinesh, thanks for those details. We have an existing enhancement to add generic SAML 2.0 support and I believe it's on the roadmap for a future release (not soon). I will add your comments to that JIRA so that engineering are aware we have a customer that would like this feature. At this time there unfortunately is no workaround therefore no support for JumpCloud.
0 -
Can you please provide us any estimation when this can be implemented ?
0 -
Dinesh, all I can say is that it will NOT be in our Q3 release due to other priorities. Planning for the Q4 release (November/ December) will start in a few weeks time and I have noted in the enhancement that this is a mission critical enhancement for you.
0 -
Thanks for confirming. looking forward for the resolution on or before that.
0 -
Hi Team,
Any update on the progress ?0 -
Hello Dinesh,
We do not have any updates to provide at this time. Thanks for checking in!
0 -
Hi Team,
As discussed, the release is planned for November/December. Could you please share an update on the current progress and confirm whether we are on track to meet the expected timeline?
This is a mission-critical requirement for us, as we are looking to transition our SSO setup from Entra ID to JumpCloud as soon as possible.
We understand that implementation may take time, but if there are any challenges or if the enhancement is unlikely to be available in the near future, we would appreciate some clarity so we can plan accordingly.
Since this functionality is important to our long-term requirements, if it cannot be delivered within a reasonable timeframe, we may need to evaluate alternative FTP platforms which supports generic SSO configuration or specific with Jumpcloud IDP.
We value our relationship with your team and would appreciate your guidance on the feasibility and expected timeline for this enhancement.
0 -
Hi Dinesh,
Our product manager informed us that our 2027.1 release will address the generic SSO support, which will include JumpCloud.0 -
Hi Jeff,
Thanks for confirming. Could you please confirm whether this patch will be released in January 2027?
0 -
Hi Dinesh,
I apologize for the delayed response. I just received word from our engineering team that we will actually be including Beta support for this feature in 2026.4. This will give you an opportunity to set this feature up, configure it, and provide feedback prior to our official release in 2027.1. Once we have this release, we will provide instructions on how to enable the Beta features in Cerberus FTP Server.
0
Please sign in to leave a comment.
Comments
13 comments