Import App Users to Okta and User assignment

Questions
1

Hello,

I trust this message finds you well. We are excited to share that our app integration with Okta, incorporating SAML and SCIM2.0 provisioning, has been successfully implemented. The User and Group APIs have been thoroughly tested and are operating seamlessly, ensuring a smooth integration experience. Our objective now is to migrate, import, and assign app users to the Okta platform.

However, we have encountered a couple of challenges during this process:

  1. Limited User Import Issue:

While attempting to import our application users to Okta, we’ve noticed that only a subset of users is being successfully imported, with the count falling short of the total 246 users.

  1. Error During User Assignment:

Upon trying to assign an imported user to the app, we encountered an error stating, “login The field cannot be left blank. Username must be in the form of an email address.” Despite our efforts to address this through mappings, both attribute mappings and the default mapped Okta Username have not provided a resolution.

We appreciate your attention to these matters and would be grateful for any insights or assistance you can provide.

2
  1. Are all users being returned when Okta hits your SCIM server’s /Users endpoint? Or is the server only returning the same subset of Users that you see imported into Okta?
  2. What information about these imported users is being returned by your SCIM server and what mappings do you currently have in place?
3

Hi @andrea thank you so much for your response.

  1. There was a pagination issue and it’s resolved now.

  2. Once the users are imported while assigning we need to specify whether it’s a new user or an existing user(there is a small dropdown-like arrow there), and then the assignment arrow turns green. I don’t understand why again we need to select it manually if the email is mapped to the username attribute.