As if Amazon® didn’t already have their fingers in many, many pies, the goliath has expanded its AWS® solution into the web application single sign-on (SSO) space with AWS SSO. With AWS SSO, many of the incumbents of the SSO scene are starting to get nervous (e.g. Okta®, Azure®, et al). After all, there are already a large number of vendors in the market, so when big companies like AWS show up with a new entry, tension ensues. In light of this new entry, we’ll pit AWS SSO vs OneLogin® (a traditional SSO solution) to see which one stacks up better.
AWS SSO vs. OneLogin
The short answer is that either could work, but it really depends upon your organization’s needs. Like many solutions under the umbrella of Identity-as-a-Service (IDaaS), both AWS SSO and OneLogin are tailored towards specific niches in the market.
As said before, AWS SSO is a fairly new solution, which is really targeted for users of AWS solutions. This means that the offering is mainly catered towards developers and operations personnel.
The core idea is to leverage AWS SSO to login easily to AWS services and a few, select web applications, all generally infrastructure related. While this is nice for the group of users in an organization that regularly use AWS products, for others, the solution is somewhat useless. After all, a Marketing or Finance team may not need access to cloud-hosted virtual machines, but would still need SSO to access their various non-AWS applications.
OneLogin, on the other hand, has been around for quite a while, offering a comprehensive IDaaS platform that is really aimed at large-scale enterprise organizations. Their catalog of web application connectors is extensive and they are not tied to an AWS identity as the source of truth. In fact, OneLogin most often works with on-prem identity providers such as Active Directory® and LDAP. Their price point and implementation strategy is also enterprise class-focused.
A constant thorn in OneLogin’s side, however, is Okta®. They are the current market leader in the SSO space, and have been for a long while now. OneLogin has been fighting an uphill battle against Okta, and with the new entry of AWS SSO, their position is even more tenuous.
The Bigger Question
While AWS SSO vs. OneLogin is certainly worth looking into, the question raises a larger one: why pit SSO solutions against each other in the first place? For most organizations, SSO is only one small part of the overall identity and access management (IAM) problems that they are facing. Ideally, modern organizations are looking for a way to have one identity for their users that can connect to a wide range of IT resources including systems, applications, files, and networks rather than being tied to one provider or working with multiple IAM solutions. Said another way, they are looking for a True Single Sign-On™ experience.
Thankfully, there is a cloud-based IAM solution that comprehensively encompasses this need in a single offering. A next generation cloud directory service, this solution ties together the functionality of an identity provider with SSO, user and system management, and more in a single browser console. All of this and more are available from JumpCloud® Directory-as-a-Service®.
Try JumpCloud Free
Instead of debating AWS SSO vs. OneLogin, try JumpCloud to solve your IAM needs. You can take advantage of the Directory-as-a-Service platform absolutely free, with ten users included at no cost, just by signing up for JumpCloud.
If you don’t want to dive right into the product, you can schedule a free personalized demo to learn about JumpCloud from an expert. You can also always contact us for more information, or check out our YouTube channel for great video content.