4.4 out of 5 (35 Ratings)
Jan 19, 2017
The product has delivered on most promises, and our end users have been very happy with the SSO experience. However, their support division can be quick to pass the buck when dealing with issues.
Jan 18, 2017
Other that a few hiccups with the service this year, the product has been flawless.
Jan 18, 2017
OKTA works preety well. It works as the main hub to all needed applications.
Jan 13, 2017
Effective pre-sales consulting engagement to design the right product configuration for our needs
Jan 10, 2017
The onboarding process for okta was a fairly simple one, we were able to get on track without a lot of technical issues occuring
Jan 10, 2017
the vendor went above and beyond to ensure that the completion date and all of the needs were met
Jan 9, 2017
The onboarding process for this system was a easy transition for the company
Jan 5, 2017
Okta enabled the institution to transision users and 10 application to single sign on and provisioning. The goal was to improve user experience and security. We found Okta to be simple and easy to use, and it certainly lived up to the sales pitch. Support was also exceptional during the traisition. Whilst we used an implementation partner, we also used internal staff to do the majority of the technical and change management work. This enabled us to use our implementation partner for advice and guidance during the planning and execution of the change. With the transistion we only had 0.4% support calls, a very good outcome for the organisation and the technical teams involved.
Dec 28, 2016
We mainly used the Okta API and the corresponding Java SDK to implement a vendor agnostic Identity and federation solution for our clients. The API was easy to use, but lacked some functionality we needed. We opened feature requests over half a year ago and none of them got any attention. They strongly suggested we used the Java SDK, which they hardly ever update, so we ended up forking the repository and creating pull requests to fix bugs or to update the SDK to match the REST api. None of our pull requests got merged. We ended up building and maintaining our own version of the SDK, which defied the initial purpose of contracting Okta. The technical person assigned to our account had no clue about our application although we explained and sent architecture documents multiple times. He kept mixing up with a different account and wanted to talk about something completely different. We sent questions in advance of our calls, but whenever we had the calls, they were unprepared and just said they were going to get back to us with an answer (although they had probably a full week to prepare). We stopped having regular calls with them for these reasons.
Dec 27, 2016
A positive experience overall. Some challenges came to light as we implemented their platform solution which we would not yet consider enterprise-level due to lack of support for multiple locales and limited flexibitlity of their two-dimensional user attributes model (preventing the definition of structured multiple permission sets for a given user). That said, the accoutn and sales teams have been quick to escalate issues internally to offer us guidance and reach resolution where possible. A related challenge was the push for us to purchase professional services whenever we had questions on implementation due to limited documentation of their platform offering. Again, overall positive experience and robust infrastructure, just needs a bit of investment to bring their relatively new platform offering up to par.