Single-Sign-On Rollout for Content Creators

CET & CET Developer: Single Sign-On (SSO) Update

We are introducing a new single sign-on (SSO) experience across CET and CET Developer. This update modernizes authentication and provides a more consistent login experience across the platform.

This change affects all CET users, with additional considerations for developers and QA specialists using CET Developer.

Release Timeline

• CET Developer (Beta) with SSO support will be available early next week
• CET 17.0 will be released on May 18, including SSO
• The CET Developer beta will be promoted to an official release alongside CET 17.0

CET: Updated Login Experience

CET will use SSO as the standard login method for users.

For automation scenarios:

• A headless login option will continue to be available
• This is intended for CI/CD pipelines and other non-interactive use cases

For most users, SSO will be the only login method they interact with.

CET Developer: What to Expect

CET Developer introduces SSO for its primary login flow, with some important behavioral changes.

When launching a version of CET Developer with SSO enabled:

• You will be logged out automatically, regardless of your current login state
• You will be taken directly to the Settings page to sign in
• Login is performed in the same location as before

Once you sign in:

• You should remain logged in across sessions
• Certain features, such as publishing extensions, require you to be logged in

For a detailed walkthrough of the new login experience, see:
https://support.configura.com/hc/en-us/articles/38926300679447-Your-Guide-to-the-New-Login-and-Sign-Up-Experience

CET Developer and 'cop'

Authentication behavior differs slightly between CET Developer and the cop tool, especially for automation scenarios.

If you sign in to CET Developer using SSO:

• cop will automatically be considered logged in

For workflows that rely on automation:

• cop continues to support a separate, optional login method
• This method does not sign you into CET Developer

Headless login using environment variables

The optional login for cop (and headless CET usage) can now be provided via environment variables:

• MCAUTOU → username
• MCAUTOP → password

When these are set:

• cop will use them for authentication
• They can also be used for headless login to CET

This is primarily intended for CI/CD scenarios.

CI/CD and Bot Accounts

Some developers have raised concerns about using personal MyConfigura credentials (email and password) in CI/CD pipelines.

To address this, Developer Support can provide bot accounts for automation use.

• Bot accounts are intended specifically for CI/CD workflows
• Each manufacturer is limited to one bot account

To request a bot account:

1. Create a new account
2. Contact Developer Support to have it configured for this purpose

Looking ahead, Configura intends to provide a way to perform CI/CD operations without requiring an account, using a mechanism such as access tokens. This is planned for the future, but there is currently no defined timeline.

Support

If you encounter any issues, contact Developer Support:

https://configura.atlassian.net/servicedesk/customer/portal/3/group/13