


When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. like any VPN, but it really isnt bad, and is a cinch if you set up your networks in a sensible way. Then this repo put together some automation for downloading, patching and compiling everything you need, and spit out a. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema. but you also need a small server to listen for a SAML response. Import the user attribute schema from the application and reflect it in the Okta app user profile. Simplifies onboarding an app for Okta provisioning where the app already has groups configured. Link Okta groups to existing groups in the application. Groups can then be managed in Okta and changes are reflected in the application. Push existing Okta groups and their memberships to the application. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password. If you want to change the default password for the pritunl admin user, type a new password in the window and click Save. Push either the users Okta password or a randomly generated password to the app. Accounts can be reactivated if the app is reassigned to a user in Okta.
#PRITUNL SAML SETUP FULL#
The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.ĭeactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app. Okta updates a user's attributes in the app when the app is assigned. Creates or links a user in the application when assigning the app to a user in Okta.
