Skip to main content

CSS v4.14.2

2026-08-05

New Features 🎉​

  • For new BCSC integrations, or existing BCSC integrations that have not yet been approved for Production, the subject (sub) claim in the token will no longer include the client ID suffix.

Example: the format will change from: D123456789123456789@<your-client-id> to D123456789123456789.

Note: Existing Production-approved integrations are not affected by this change. This update aligns BCSC with identity providers that support Pairwise Pseudonymous Identifiers (PPID).

  • Exporting user role assignments for an integration now includes the GUID in the exported file.
  • Simplified CSS team invitation and membership management. CSS team administrators can now add admins and members directly without a pending approval status, making it easier for application teams to manage team membership.
  • With Keycloak 26.6 now deployed to Production, we have aligned our redirect URI validation with the new Keycloak requirements. In this version, client redirect URIs can no longer use wildcards in the hostname. For more information, see the Keycloak Upgrading Guide.

Bug fixes and enhancement 🐛​

  • Fixed an issue where the UI refreshed immediately after adding a role to a composite role. Users can now add multiple roles to a composite role in a single session, as intended.
  • Simplified integration process email notifications. Previously, users could receive two separate email notifications for the same integration change. Since integration updates are now provisioned almost instantly, a single notification is sufficient.

Miscellaneous 🧩​

  • Updated the home page image and documentation links to reflect the latest application status and resources.