Testing

SSO and SCIM testing

Test SSO and SCIM by signing in to Docker Desktop or Docker Hub with the email address linked to a Docker account that is part of the verified domain. Developers who sign in using their Docker usernames remain unaffected by the SSO and SCIM setup.

[!IMPORTANT]

Some users may need CLI based logins to Docker Hub, and for this they will need a personal access token (PAT).

Test Registry Access Management and Image Access Management

[!WARNING]

Communicate with your users before proceeding, as this step will impact all existing users signing into your Docker organization.

If you plan to use Registry Access Management (RAM) and/or Image Access Management (IAM):

Ensure your test developer signs in to Docker Desktop using their organization credentials
Have them attempt to pull an unauthorized image or one from a disallowed registry via the Docker CLI
Verify they receive an error message indicating that the registry is restricted by the organization

Deploy the Docker settings and enforce sign-in for a small group of test users via MDM. Have this group test their development workflows with containers on Docker Desktop and Docker Hub to ensure all settings and the sign-in enforcement function as expected.

Test Docker Build Cloud capabilities

Have one of your Docker Desktop testers connect to the cloud builder you created and use it to build.

Test Testcontainers Cloud

Have a test developer connect to Testcontainers Cloud and run a container in the cloud to verify the setup is working correctly.

Verify Docker Scout monitoring of repositories

Check the Docker Scout dashboard to confirm that data is being properly received for the repositories where Docker Scout has been enabled.

Verify access to Docker Hardened Images

Have a test developer attempt to pull a Docker Hardened Image to confirm that the team has proper access and can integrate these images into their workflows.