Multi-factor authentication integration is reliable but the use case scenarios of our business need limited its usability.
- Centralized identity management was a key feature for an on-premise password manager especially now that many systems are segregated, regardless of how integrated an ecosystem may be with Secure LDAP, Single Sign-on or multi-app software (for example, Atlassian Suite). There are many that are free but becomes a task to manage. Hands down, the best feature.
- Mobile functionality was also key, it allowed remote users to access self-service functionality or manage their passwords through their mobile device which extended their ability to work if a workstation became unavailable, at a meeting, while also implementing into the DRP and BCP.
- Self-Service password management meets the standards, especially with a self-hosted solution. Cloud-based solutions are equally as susceptible to attacks as an on-premise solution and most stakeholders prefer the latter.
- Help-Desk functionality similar to OneIdentity Self-Service Password Manager, as it provides additional users that do not require administrative access to assist with managing end-users who may have locked themselves out of HyperSocket Access Manager by forgetting their own security questions.
- Too many features which become unusable and feel like the payment plans are not flexible since it's an all-in-one product with one price. It is not necessarily a bad thing as most subscription-based pricing forces a buyer to pay more for an integral service that is only available on the highest price-plan. You really do get what you pay for, but we found many of our use-case scenarios limited the product.
- This isn't necessarily against the product, just a personal opinion around Multi-Factor authentication which is always primarily driven mobile devices. Not all companies or end-users have access to a multi-factor device, (or in our case, are allowed to have access to a cell phone while servicing members/clients). This creates a shortfall to allow multi-factor functionality to extend to all users unless there are hardware tokens, which can be miss placed or left out more easily as most users don't treat it the same way they would their personal smartphone.
It has great flexibility with multiple domains, and the ability to sync or not sync passwords between primary and secondary accounts.
I'd like to see a more granular set of permissions for the help desk role tied to an OU path rather than a whole directory. You can [create this] by defining multiple directories based on OUs but is less flexible this way.
Hypersocket Scorecard Summary
Hypersocket Support Options
|Free Version||Paid Version|
Hypersocket Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux, Mac|
|Mobile Application:||Apple iOS, Android|