I am a Zivver admin
Configure and manage Zivver
Just-in-time Provisioning for User Accounts
Introduction
The Just-in-time Provisioning solution automates the creation of user accounts in Zivver when users log in using Single Sign-On. This cloud-based solution eliminates the need for manual account creation in the WebApp or setting up the Synctool or Cloud Sync to pre-synchronize accounts from source systems. By leveraging this solution, deployments can be simplified and the adoption of Zivver within your organization can increase.
When a user logs in with Single Sign-On, their Zivver account is automatically created using the information provided by the Single Sign-On application. The user is seamlessly logged in to Zivver without any noticeable interruption caused by the account creation process.
In addition to using the WebApp, Synctool, or Cloud Sync for creating functional accounts and performing other account management actions, you can also use Just-in-time Provisioning for user account creation.
Prerequisites
- Your Zivver organization must use Single Sign-On.
- Your Identity Provider’s SAML response needs to be amended with a Zivver DomainKey.
Configuration
If your organization uses Entra ID, follow the steps in Configure Just-in-time Provisioning with Entra ID.
For other Identity Providers (Okta, AD FS), please create a support ticket if you want to use Just-in-time Provisioning. Include in your request which Identity Provider your organization uses. Zivver Support can help you configure Just-in-time Provisioning.
Configure Just-in-time Provisioning with Entra ID
Configuring Just-in-time Provisioning with Entra ID takes five steps:
| Step | Action | Who |
|---|---|---|
| 1 | Add the ZivverDomainKey as a claim in Entra ID | Your administrator |
| 2 | Send the full claim name to Zivver | Your administrator |
| 3 | Zivver enables Just-in-time Provisioning for your organization | Zivver |
| 4 | An administrator logs in via SSO | Your administrator |
| 5 | Test with a new user | Your administrator |
Prerequisites for Entra ID
- Zivver is already connected to Entra ID via SAML Single Sign-On. See SSO with Microsoft Entra ID.
- You have an Entra ID administrator account with permission to edit the Zivver Enterprise Application.
- You have a password manager or another secure location to store the ZivverDomainKey.
Step 1: Add the ZivverDomainKey in Entra ID
The ZivverDomainKey is a fixed, secret value that is the same for your entire domain. It is used to encrypt your data. Based on the zero-knowledge principle, only your organization knows this value, not Zivver.
- Use a long, strong value of at least 32 characters, with uppercase and lowercase letters, numbers, and special characters.
- Store the value immediately in a password manager or another secure location. Zivver cannot recover this value if you lose it.
- Do not share the value with anyone, including Zivver. Do not show it on screen during a screen share.
- Go to Microsoft Entra admin center and log in as an administrator.
- Search for and open Enterprise applications.
- Search for
Zivverand open the Zivver application. - Click Single sign-on (or the tile 2. Set up single sign on).
- Click edit Edit at Attributes & Claims.
- Click add Add new claim.
- At Name, enter
ZivverDomainKey. Leave Namespace empty. - At Source, select Attribute.
- At Source attribute, type your chosen secret value between double quotation marks, for example
"<your-secret-value>", and press Enter.
This makes it a fixed value instead of a user attribute. - Click Save.
- Check that the claim
ZivverDomainKeynow appears in the list of claims.
Step 2: Send the full claim name to Zivver
To configure Just-in-time Provisioning for your organization, Zivver needs the full claim name (including namespace) of the claim with the value user.userprincipalname.
- Stay in Attributes & Claims of the Zivver application.
- Find the claim with the value
user.userprincipalname. - Note the full claim name as shown in the Claim name column, including the namespace.
- Send the full claim name to your Zivver contact person.
Example of a full claim name:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
Step 3: Zivver enables Just-in-time Provisioning
Based on the information from step 2, Zivver configures Just-in-time Provisioning for your organization. You do not need to do anything. You receive confirmation from your Zivver contact person when this is done.
Step 4: An administrator logs in via SSO
After the confirmation from Zivver, an administrator of your organization logs in to Zivver via Single Sign-On. This login is required to activate Just-in-time Provisioning. Tell your Zivver contact person when this is done, so Zivver can check that the configuration is active.
Step 5: Test with a new user
Ask a (test) user who does not yet have a Zivver account to log in to Zivver. The user is redirected to SSO and automatically receives a Zivver account after logging in. If this works, Just-in-time Provisioning is set up successfully.
If you have questions, contact your Zivver contact person or Zivver Support.
Limitations
Domain limitation
Just-in-time Provisioning can only be used for one domain per Zivver tenant.
User account limitations
The following account management operations must still be performed manually in the WebApp or by using the Zivver Synctool or Zivver Cloud Sync:
- Update the name or email address of a user account
- Suspend or delete a user account
- Add or remove delegate access to a user account
- Add or remove email aliases
- Assign a user account to an Organizational Unit in Zivver
- Special functions such as updating the ZivverAccountKey
Functional account limitations
Just-in-time Provisioning only supports user accounts. This means that for functional accounts, the following account management operations must still be performed manually in the WebApp or by using the Zivver Synctool or Zivver Cloud Sync:
- Create a functional account
- Update the name or email address of a functional account
- Suspend or delete a functional account
- Add or remove delegate access to a functional account
- Add or remove email aliases
- Assign a functional account to an Organizational Unit in Zivver