Cerberus Feature Requests - Voting
Pinned Featured
Hello from all of us here at Cerberus!
We wanted to reach out to all of our users that take part in making suggestions for the betterment and improvement of Cerberus, and first of all, thank you for contributing. Without feedback from our users, Cerberus would not be able to grow and evolve into the platform it is today, shaped to fit our users, by our users.
Making decisions on what feature request makes it into which release, is a complex but very important process here at Cerberus. There are many different variables that contribute to how we make these choices. As you might have noticed, within the Feature Requests forum, there are two different numbers that are tracked to the right of a post. One is comments, the other is votes.
We would like to make sure that the importance of votes is communicated to those using the forum, as this is how we can easily tell how important any one feature may be to the larger audience. If we see that a post is very important to a lot of different users, it tends to get more traction than those that do not. As much as we would like to take every feature request and put it right into use, we must prioritize which comes first. Voting on feature requests is an important part of getting feature requests implemented in a timely manner, and into the hands of our users.
If you see a feature you like, or think is important, hit that up arrow on the post. Even upvoting comments will improve a feature requests' total vote count!
Highlighted on the right hand side of this post, you can see the up and down arrows. Using the up arrow will give the post will add 1 total point to the vote count, while using the down arrow will subtract 1 total point to the overall vote count.
Once again, thank you to everyone who is helping us improve our product, to better serve our users!
-
FortiAuthenticator approved SSO IdP-
I had this working briefly in a March-April of 2026. SCIM was also provisioned and was working accordingly. Since then I cannot seem to replicate my success. Receive "SAML : Validate Response : Signature validation failed. Check that the SSO configuration has the same signing certificate as the Identity Provider"
Due to updates on both sides, I could not determine why it stopped working. I assume it was how either FortiAuth sends certificates, or how Cerberus reads the incoming certificate as to why it continually fails.0 -
Hello Zach,
If you're posting to have this turned into a feature request, please comment here: https://support.cerberusftp.com/hc/en-us/community/topics/200198295-Feature-Requests
With your enhancement, and just make sure it follows our guidelines, here: https://support.cerberusftp.com/hc/en-us/community/posts/1500000413782-Feature-Request-Guidelines
If you are looking for troubleshooting, you can send us an email at support@cerberusftp.com or https://support.cerberusftp.com/hc/en-us/community/topics/200198285-Troubleshooting-Tips
Thanks so much!0
Please sign in to leave a comment.
Comments
2 comments