qvx83 (qvx83) asked a question.
Use a *non default user type/schema* to provision users from upstream application
I currently am using two upstream services to provision users into my Okta instance. I would like them to provision users with a different user than the "Default User" type. I have created alternative user types to migrate users over to a different mapping set, but am not able to automatically provision users under those schemas. Any approaches to get applications to pass users to a non-default user type?
Hello @qvx83 (qvx83),
Please check the following link qith information: https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-user-types-known%20issues.htm
Regards,
Natalia
Okta Inc.
Thanks @User16254393570754125507 (Okta) -- From this, I'm understanding that user type is useless for systems relying on automation (eg group assignment, not being able to choose a specialty user type) or for managing migration. Is that accurate or are there relevant times user type is relevant? I am trying to understand if I should disable the use of secondary user types by default, as it sounds like it will be a risk if folks do mappings for those users only but the default user is used for SAML, etc..