DigiCert® ONE version: 1.6392.1 | Account Manager: 1.812.01
Starting November 1, 2023, at 18:00 MDT (November 2, 2023, at 00:00 UTC), we will require all DigiCert ONE accounts to use two-factor authentication (2FA).
You will use both your credentials and a one-time password to access your account. When you log in to your DigiCert ONE account on November 1, you will be prompted to set up two-factor authentication. If you have already enabled two-factor authentication in Account Manager before this date, no further action is necessary.
How to enable two-factor authentication in Account Manager.
Nota
If you use single sign-on (SSO) to access your DigiCert ONE account, the new two-factor authentication requirement does not affect you. However, the requirement will activate if you modify your SSO settings.
Minor updates to roles and permissions
Minor bug fixes
DigiCert® ONE version: 1.6201.1 | Account Manager: 1.796.0
Fixed bug that prevented quotation marks in organization name.
Made the zip code optional when creating a new account.
DigiCert® ONE version: 1.5428.1 | Account Manager: 1.706.0
Audit logs in Account Manager can now be pulled using an API.
Fixed issue where special characters (such as "Ü") were not supported in account names.
DigiCert® version: 1.5118.10 | Account Manager: 1.695.0
DigiCert One Account Manager will be replacing permissions with role-based access.
New users are required to select a role upon creation.
Current users are not required to make a change unless they attempt to edit their current user permissions.
Users can select from a number of pre-defined system roles, or create custom roles with specific permissions for specific needs.
Access management of custom roles from the Access page within Digicert ONE Account Manager.
DigiCert® version: 1.5118.3 | Account Manager: 1.666.0
Users can now use the Enter key to proceed on the login page.
Fixed issue with adding organization contacts for Japanese language users.
DigiCert® version: 1.4957.1 | Account Manager: 1.634.0
After a user logs out of DigiCert ONE, they are taken to a login page that is based on the authentication preference set in their account.
Fixed an issue where on-premise users were not seeing custom features (such as a logo) on the login screen with the new two-step login flow.
Fixed an error that occurred on login when MFA was enabled on accounts and a new user was created.
When a user attempted to log in with an incorrect username, they were taken to an error page instead of receiving an error message.
DigiCert® version: 1.4803.0 | DigiCert Account Manager: 1.616.0
Users now see a split login page. They will enter their username on the first page, then are directed to a second page to finish authentication. This allows for a wider range of authentication methods.
Documentation links go to the documentation specifically for the DigiCert One manager that the user is using.
Fixed an issue where a user was required to enter a device name when resetting 2-factor authentication.
Added new API endpoint that allows users to filter by active or disabled service users.
When editing the city name in an organization, we previously did not allow special characters. There are some specific special characters that are in city names (e.g. hyphen) which we now allow.
Updated MariaDB from version 10.3 to 10.6. Users with on-premises installations may wish to upgrade MariaDB in their environments.
Fixed an issue where users encountered a blank page after signing in to their account.
Fixed an issue where edits to an existing service user failed to update.
Users using SAML to log into DigiCert ONE will receive an email notifying them of IDP certificate expiration.
Provided support for CSC v1 APIs.
Improved and simplified onboarding flow for DSM customers.
Fixed issue where names were not displaying correctly in email notifications for client auth certificate expirations.
Fixed an issue where DigiCert ONE did not display product names correctly.