OktaBGI.92523 (Customer) asked a question.
We have configured provisioning for Cisco Webex using the template in the OIN. We made no changes to the default profile mapping for the app. It seems provisioning fails if a user has a space in the the Okta State field, which maps to Region in Webex (these are non-US users who do not have a state). We see the failed task on the dashboard under 'Application Assignments Encountered Errors' with "error = 'addresses.region length must be between 1 and 64;code=400;errorCode=100018". We are not sure why this is failing if state is space, but if state is set to null it works fine.
If we have the value for state attribute updated to null in AD and reprocess the failed transaction in Okta, the user is provisioned into Webex, but an error now shows up on the Dashboard under 'Profile Push Errors' - "An error occurred while pushing a profile update to this app.Automatic profile push of user fname lname to app Cisco Webex failed: Error while trying to push profile update for fname.lname@company.com: Bad Request. Errors reported by remote server:".
Is there a step we are missing in order to clear this error? Has anyone come across something similar to the above scenario? Thanks
Hello,
In researching, one possible cause is the user already has an account with the service provider with the same username that your Okta integration is trying to push.
Can you find out if the user have their own account in Webex, and if so, was it created under the same username or email address?
If so try to un-assign and re-assign a user back to the WebEx application. But before doing so please make sure that Deactivating is not enabled on the Provisioning Tab for WebEx in Okta
https://support.okta.com/help/s/article/User-profile-updates-aren-t-being-pushed-to-the-application-after-we-enabled-provisioning?language=en_US
Thank you.
That would appear with the following message in Tasks if the user has created a free WebEx account online -
An error occurred while assigning this app.
Automatic provisioning of user John Doe to app Cisco Webex failed: Error while creating user John.Doe@email.com : Conflict. Errors reported by remote server: User exits already
Yes we do get the error 'user exists already' if the user has created their own account previously, we know the process to resolve that is to have the Webex Admin 'claim' the user account in Webex. These 'Bad Request.....' errors are different. We continue to work with Webex - who is attempting to work with Okta - to determine the cause.
We have the same problem, this message never appeared when we first started to provision users to app WebEx in Okta so it's strange why it's suddenly started appearing in Tasks for any new provisioning to WebEx app for users -
An error occurred while assigning this app.
Automatic provisioning of user John Doe to app Cisco Webex failed: Error while trying to push profile update for john.doe@email.com: Bad Request. Errors reported by remote server:
From what I heard speaking to a colleague this has been raised with Okta and Cisco however both blaming each other for the message, not sure if this will ever be resolved as I've tried the basic deactivate users, reactivate and remove from WebEx app and re-provision but still get the above message in Tasks.
Thanks for the info, it's nice to know we are not alone. We are finding the same - we have cases open with both Okta and Cisco, and each blames the other. Please post back if you ever get a resolution and I will do the same.