Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂
To learn more about our Ideas Portal, check out our FAQs.To schedule a feedback session with a member of the Liongard Research Team, click here.
See what we've shipped by clicking here!
Hi Everyone, we're currently working on capturing all the requirements necessary for implementing SSO but it is on the roadmap. We're keeping an eye out on your feedback and will keep you all updated. Thanks again for your feedback!
SSO is crucial. Admin's come and go and you need the ability to lock out there AD account and then have their access to Liongard get disabled.
SSO should be the standard for every application that isn't directly integrated with a IDP.
Thinking again - you could also offer your own MFA for those who are not interested in SSO or consolidating with a vendor. It's more work, and it is another TOTP to manage, but the flexibilty of that and SAML might be nice for everyone.
Hi folks - I lead Evo Security, all we do is MFA, SSO and PAM for MSP's. I would definitely agree that the most effective use of resources for liongard is to support standards. Starting with SAML provides the most flexibiity for MSP's to use any MFA/SSO vendor of choice. Building an internal liongard MFA system would mean MSP leaders and teams must scan another QR amongst the 10's of others TOTP's in a mobile app (or apps). With SAML, the TOTP can be consolidated in one single TOTP along with the other applications that vendor integrates with. Regarding Azure, the right MFA/SSO vendor can simply sync with Azure AD or via LDAP for on-prem AD, so no need to build in something custom for Microsoft here. SAML and you're golden :)
Azure AD/SAML with Role/Privilege's assignment and auto provisioning.
Please and thank you!!
Azure AD / SAML yesterday please. Admin response says that it's on the roadmap, where on the roadmap is it?
SAML would allow us to use Duo Gateway (but is also a standard that would allow most clients to pick their preferred auth gateway... whether it be Azure AD, Duo, Okta, etc.) but would be flexible enough to still allow LionGard devs to have one method/interface to configure this and support.
Agreed with others... support SAML not a specific vendor please!!!
Another +1 for SAML?Azure AD. The defacto standard for all systems.
I would prefer SAML/ADFS/Azure AD above a DUO intergration. it's more flexable
Azure AD / SAML - do not lock in with one provider!
I would also prefer a general SAML Support - we don't use Duo.
Support standards, not individual vendors! SAML first please.
Guys, please support ADFS integration! this would make life a lot easier and gives us better integration with Roar!
+1 for SAML 2.0 and WebAuthn, Okta is the market leader for this: https://developer.okta.com/
+1 for SAML. We previously used Duo SSO and it was far too limited with many systems not supporting it, ConnectWise being the biggest offender. It also requires an on-premise server to host, meaning you need to setup an HA server setup to ensure consistent login access.
We moved to Azure SSO for all apps and it works much better.
+1 for SAML/AzureAD
SAML for more than just duo would be ideal. Okta is a leader in SAML authentication, and we'd like to see support for that as well
Agree with other comments, please provide SAML 2.0 support over Duo for SSO, and FIDO2 support over Duo for MFA. Also combine the Liongard app, Liongard docs, Liongard ideas and Liongard Support into a single account.
You won't be notified about changes to this idea.