| Push new users |
- New users that you create in Okta are created in the Progress Chef org tied to the API credentials used for the integration.
- For non-governance orgs, the default roles org-viewer and tenant-viewer are assigned automatically.
- In Okta Identity Governance orgs, you must assign a user role. Both standard roles and custom roles are supported.
|
| Push profile updates |
- Updates that you make to a user's first name and last name in Okta are applied to Progress Chef org.
- You can't update the username or email address.
|
| Push user deactivation |
- When you deactivate a user or remove their access to the app in Okta, they're also deactivated in the Progress Chef org.
- Deactivation is a soft delete. The user record is retained, but the user can't sign in.
|
| Reactivate users |
- When you activate a user in Okta, the user is also activated in Progress Chef.
|
| Import new users |
- Okta imports active users in your Progress Chef org.
- Users who are active in Progress Chef org but inactive in Progress Chef tenant aren't imported into Okta.
- Progress Chef doesn't support groups, so you can only import users.
|
| Entitlement Management |
- You can manage app entitlements for Progress Chef in Okta. Entitlement management requires Okta Identity Governance.
- The integration supports a single, multi-select User Roles entitlement. Both system roles and custom roles are supported.
- Progress Chef automatically adds its default roles to new users.
|