Has anyone used OKTA with Appian?

I am aware of OKTA (SAML) being used with Appian. On the Appian side, the steps that were followed are described here: forum.appian.com/.../Appian_Administration_Console.html

My team just tested with OKTA as well, worked like a charm and took <1 hr from nothing to working.

Thank you for the information. One other question. How did you configure Okta? Do you login to Okta and then Appian or Appian and authenticate through Okta?

Our test run was just a proof of concept but we configured a specific group of users to get authenticated through SAML. They would have to login to OKTA first before continuing into Appian, attempting to go to our application URL autoredirected to the OKTA login. I don't believe that was configurable in the brief look we took but I'm not sure.

However our use case involves users outside the core group that don't authenticate via SAML, for them the trick appears to be to send them directly to the url ending in <appian_home>/suite/login.jsp where they can login normally.

Please reply back if you find anything else. We won't be implementing SAML for a few more months at the earliest.

Thank you for all of the information. When wee implement our Okta integration I will update this thread with any additional information that we find.

Hi Jesset, Helmuta, we are looking at Okta, OneLogin and Centrify for an identity provider. So far, Okta looks good. Have you completed your installation yet?
In addition to our external customers, we are also looking at federating our AD users into the identity provider namespace.

Yes, our production environment is has been working with Okta very well. We have also used the API from Okta to gather additional information about our users. It was a breeze to setup.

hi helmuta, good to hear that it is working well for you. So do you have all your users being authenticated via Okta and have the redirection parameter checked so that anyone that tries to login via your Appian login page gets redirected to the Okta login? When a user gets a task notification and they click on the link, do they get redirected to the Okta login page and then when they login, does it take them to the task?
Also, are you able to give me an idea how Okta charges for its services? We have potentially 25000 users but only 10-15% would be logging in during a given month.

No idea on the charges.
Yes, all of our internal users are being authenticated through Okta. We do have a couple of external users and some of our admin accounts that use what we call the workaround. Rather then going to company.appiancloud.com/.../tempo they use company.appiancloud.com/.../login.jsp. In this way you can have users that do not have to authenticate through Okta but use the internal (Appian) authentication.
Task notifications go directly to the task if the user has already logged into Okta. Otherwise they are redirected to login to Okta and then go to their task.

OK thanks for the info. Are your internal users on AD or an internal LDAP directory and then syncing into the Okta namespace or are all your users in the Okta namespace and of course, in the local Appian namespace?
We want our external users to be in the Okta namespace and our internal users still in our Active Directory.