What Oleria discovers
User accounts and profile attributes synced from Docker Hub’s directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Oleria’s regular sync schedule.Prerequisites
- Admin access in Docker Hub with permission to enable SCIM provisioning and generate a SCIM token.
- A Docker Hub plan that includes SCIM provisioning (Docker Business, with SSO configured).
- Admin access on the Oleria platform to add a new integration.
Get your SCIM credentials from Docker Hub
1
Enable SCIM provisioning in Docker Hub
Sign in to Docker Hub as an admin and turn on SCIM provisioning in Admin Console > Security > SSO and SCIM. Then generate a SCIM token.
2
Copy your SCIM Base URL and Authentication Token
Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
- SCIM Base URL - the SCIM 2.0 endpoint Docker Hub shows when you enable provisioning.
- Authentication Token - the SCIM bearer token.
Copy the token now and store it securely. Rotate it per your organization’s security policy.
Connect Docker Hub to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the Docker Hub tile.
2
Complete the connection form
Fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
Verify the integration
Confirm the new instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. Oleria syncs users from Docker Hub on its regular sync schedule once the initial sync completes.If you regenerate the SCIM token in Docker Hub, update the Authentication Token in Oleria by editing the integration.
Remediation actions
Oleria can also take these actions in Docker Hub when the SCIM token can update users:- Enable or disable a user account
- Create a new user
Oleria doesn’t check the SCIM token’s permissions until an action runs. If an action fails, confirm the SCIM token can update users in Docker Hub.