How to configure Okta provisioning using Multi-Provider SSO?

[bodenlarson]

Hello - very new to ServiceNow and probably getting ahead of myself.

We will use both Okta SSO and native ServiceNow logins.   I've configured the Multi-Provider SSO plugin, and can login with the admin account and an SSO account without incident.   So far so good.   However, when I try to enable provisioning in the Okta app (ServiceNow - Eureka and later releases), it fails when checking the ServiceNow account used for provisioning (in this case, just admin).   The error I get from Okta is:

Please review the form to correct the following error(s):

• Could not verify the ServiceNow administrator login and password; please confirm that these are set correctly.

I don't see login attempts in the event log after doing this.

On a possibly related note, I cannot get the Help the Helpdesk script to push data into ServiceNow either, regardless of browser, etc.   I think I'm missing something very basic.

[tony_barratt]

Hi Boden,

There are configuration steps here, which I guess you have been following

ServiceNow Provisioning

What results do you see if you

Click the Provisioning tab

Click Edit, then click Test API Credentials

?

The issue might be related to the ServiceNow admin user and the password defined.

Best Regards

Tony

[bodenlarson]

Hi Tony -

I've followed the guides, and do have SSO itself working with Okta as an IdP.

When I click the Test API credentials button, I receive the error I indicated in the original post:  

Please review the form to correct the following error(s):

• Could not verify the ServiceNow administrator login and password; please confirm that these are set correctly.

I have double and triple checked the password and user id ("admin").   I've also tried the admin account's email address instead of id.   Not sure what to do at this point.   Is there some sort of basic security configuration that I could be missing?

[JV6]

Hi were you able to get this working?

I have the same problem. Mine stemmed after we did a rename of our instances.