IDP Provider Configuration

[Rob_Lewis2]

We have IDP installed and working. 

We have actually created some further ISP providers and the Type is OIDC-Exchange.

These are so we can use Named user accounts with some external Portals.

We had an issue because we missed the "Strip domain from username" and because of this is created a new user. 

We resolved this by checking it and from there it has not created any new users.

So, based on this I have a question and an issue.

Question

Under the User Provisioning Section, what do the options actual do? If we uncheck both the "User Provisioning Create Enabled" and 
"User Provisioning Update Enabled" will this cause any issues? We do not need the 2 new ones to create users and have kept them checked in the main IDP Provider.

What do they actually do? Cannot find any documentation about this.

Issue

When we first configured the new provider as stated we missed the "Strip domain". We did fix it nut then we also deleted the unwanted user. BUT now when we try to connect the API is still trying to call the deleted user. The diagnostic logs show that when the user tried to connect it is looking for the deleted OnBase user. We can see through the ID. So always fails.

It is only one user and the user that first logged in a s stated earlier.

Any ideas on that would also be awesome.

Thanks, in advance

[AdamShaneHyland]

Hey @Rob Lewis ,

The User Provisioning settings ...

... allow the Hyland IDP to create and/or update the user account AND assign the user to mapped User Groups.   You can reference the documentation for more information about the Provisioning settings.  This link is for the Hyland IDP 3.0 and for the OIDC Exchange Provider ...

https://support.hyland.com/r/Other/Identity-and-Access-Management-Services/3.0/Identity-and-Access-M...

With respect to the issue you referenced, you can look at the Hyland Diagnostic Logs, specifically the Hyland.Identity.Provider profile and the ApiServer profile to see more information about what is occurring.  Likely you'll need to increase the logging level.  You may see an error message under the LogLevel if you filter on Error.

However, this will likely take a deeper level of investigation than is efficient through Community.  I would recommend submitting a Support Ticket for the issue.

Best wishes.