Sorry, I know you were probably looking for a concrete answer, but setup time truly depends on a few factors. For example, how do you define setup, how complex is your organization, and what will provider support look like?
I can tell you, though, an IDaaS setup doesn’t take nearly as long as a typical on-prem setup does.
Let’s take a look at those specific factors.
How do you define setup?
After you’ve taken time to research and test different providers, getting started with a cloud IAM solution (depending on the provider) can take as little as a few minutes. This generally includes single-sign-on (SSO) and sometimes, multi-factor authentication (MFA).
A common step for implementing SSO often is to integrate with the company’s on-premise directory. For example, to integrate OneLogin with Active Directory, you have to install OneLogin’s Active Directory Connector (ADC), which itself takes only a few minutes with a simple click-through, zero-config process once you have gathered the necessary details. Adding applications is also easy, since OneLogin comes with thousands of pre-integrated apps. We’ve seen IT departments implement SSO and add MFA in anywhere from 1–10 days.
If setup means rolling out with all the features a provider boasts (e.g. SSO, automated user provisioning, MFA, policy-driven security, etc.), then it’ll certainly take more time—perhaps weeks instead of days. So, you’ll want to identify and prioritize the identity challenges you’re trying to solve.
How complex is your organization?
Since every organization looks different, some require longer timeframes for fully setting up a cloud IAM solution than others. As mentioned above, the features—and deciding on the ones you need—affect the timeframe, and so does the complexity of your organization.
Size and Location
Are you trying to roll out applications to 12 different departments? Does your company have multiple on-premise directories?
Most cloud IAM solutions scale well with size of users and amount of applications, so it’s the number of departments that affect setup time. It’ll take time to work with each department to make sure each one knows how an IAM deployment impacts them. Also, the more directories to integrate into one centralized place, the longer the setup time.
Internal and External Users
The work of actually setting up the users is as easy as the IAM product is to use. What takes time though is thinking through how you want to define which users get access to what applications. OneLogin allows you to create roles, groups, and mappings to automate this. So if you only need to plan out a few roles, groups and mappings for internal users, then it’ll take less time than if you need to plan out extra ones for providing application access to external users, such as contractors.
For instance, OneLogin’s Professional Services Team was able to deploy the applications and technology of Children’s Healthcare of Atlanta—600 internal and 4500 external users—in a week. Although a faster than normal timeframe, this is a great example of OneLogin being a straightforward and simple solution for what is often a complex problem.
What will provider support look like?
Professional Services Team
The fastest way to set up a cloud IAM solution is to let the pros do it. A provider’s professional services team will help you set up not only faster than you could on your own, but also to the solution’s maximum potential because they know their solution inside and out.
A number of vendors have genuinely helpful online Help Centers—which means, no joke, your setup timeframe depends on how quickly you can read and understand the support pages. Vendors also offer support over the phone. When you test a provider, consider how easy their solution will be to set up and maintain yourself and how helpful their phone and online support is.
Are you ready to do just that for OneLogin? Request a demo before starting your free trial.