The following information describes new features, updates or changes to Certara Admin. For a complete list of all changes, including bug fixes, please see the Release Notes.
Users
Sign in page
We've enhanced the sign in page. Depending on your organization's configuration, you may now see the following:
Instance type
A message now indicates if you are signing into a non-production instance (e.g. sandbox, staging, or other).
New users must sign in using SSO
If configured by your organization, a message will inform new users that they must sign in using Single Sign-On (SSO).
All users must sign in using SSO
If required by your organization, the page will state that all users must sign in with SSO.
Multiple SSO options
If your organization has multiple SSO providers, you will now see a separate sign in button for each. Administrators can set display names for each SSO option, for example, "Single sign-on (SSO) for internal workforce".
Sign in to Phoenix Hosted with your Certara ID.
You can now use your Certara ID to sign in to applications like Phoenix Hosted, thanks to new Single Sign-On (SSO) support. This simplifies access by letting you use a single set of credentials for the hosted virtual desktop and all supported Certara products.
Administrators
Single Sign-On
General SSO Settings
To better support multiple SSO identity providers (IdPs), the following global settings have been grouped together on the SSO Settings page:
Require user creation through SSO
Require user sign-in through SSO
Log users out from IdP when logging out of Certara
These settings may impact the login pages shown above.
Note: To change the SSO configuration name, SSO button label or to activate multiple SSO configurations, contact Certara (your Customer Success Manager, open CASD ticket, or email [email protected].)
SAML User-creation and Deactivation
Certara users can now be created or deactivated by your IdP using the SCIM protocol and an authentication token. For IdPs configured with the SCIM token, users are created or deactivated in your organization based on the rules you set in your IdP.
Important Notes:
If the user already has a password-based account within the organization, their account is converted to an SSO-managed account.
A user’s email address must be unique within an organization.
If multiple IdPs are configured:
When you create a user with SCIM, they are automatically associated with the Identity Provider (IdP) linked to that SCIM token.
You cannot use SCIM to manage a user who is already associated with a different IdP.
Audit logs show created or deactivated users being modified by SYSTEM.
Notifications
Improved user-blocked notifications
The email notification sent to administrators when a user is blocked now includes more detailed information to help you troubleshoot faster.
The "User is Blocked" email notification now includes:
The reason the user was blocked, such as:
Multiple failed login attempts
Attempted login from a blocked IP address.
The product or service that the user was attempting to access:
The product the user was trying to log into
The Product Environment URL.
The specific Organization Name or instance.
The user-blocked email also now includes a link to a help article with instructions on how to unblock users.
Change of email address notification
When a user's email address is changed, an email notification is now sent to all Global Admins and any Product Admins for products assigned to that user. Previously, only the impacted user was notified.