You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
Lots of corporate environments do not have Okta, OneLogin, etc to authenticate with. Good ol' LDAP/Active Directory is the only identity management solution available to us.
Steps to reproduce: Don't have Okta or OneLogin. Have LDAP
Earliest version known to be an issue: v0.10.0
The text was updated successfully, but these errors were encountered:
Yes, the feature makes sense. This is not currently a priority for the core Cerberus team but we'll gladly accept a pull request if someone wants to implement.
Implementing the Okta connector recently only took about a day or two but implementing one for LDAP is probably quite a bit more work.
Also, for anyone considering this, LDAP tends to get setup behind a corporate firewall so ports would need to be opened for Cerberus to communicate with it. A nice advantage of products like Okta and OneLogin is that you don't need to open your corporate firewall up for a single app (like Cerberus), plus Multi-Factor Authentication (MFA), etc.
No, I hear all of that, preaching to the choir. A lot of environments are not quite that far along with their identity management, so the LDAP solution is the next best option.
Lots of corporate environments do not have Okta, OneLogin, etc to authenticate with. Good ol' LDAP/Active Directory is the only identity management solution available to us.
Steps to reproduce: Don't have Okta or OneLogin. Have LDAP
Earliest version known to be an issue: v0.10.0
The text was updated successfully, but these errors were encountered: