Switch your browser used for sign-in
DigiCert ONE Clients 1.9.0 and later uses your operating system (OS) default browser to sign in to DigiCert ONE, except in specific scenarios. Versions earlier than 1.9.0 use the in-app browser and can’t be configured to use your default browser.
Using your default browser lets you use browser features such as:
Password managers
One-time password (OTP) generators
Other browser-based authentication tools
Use this guide to learn how to configure version 1.9.0 or later to use the in-app browser instead of your default browser.
Before you begin
Ensure that you’re using DigiCert ONE Clients version 1.9.0 or later.
Switch to the in-app browser
The ability to switch your browser doesn’t appear in the app menu. If you prefer to use the in-app browser for sign in, you can configure this by editing the local configuration file.
Open the config.json file on your computer:
[Your HOME]\.digicert-ucpc\config.json
In the backends section, add the following setting:
Example:
"dconeForceInAppSignin": true
Astuce
If you’re adding this setting after an existing property, make sure the previous line ends with a comma (,).
Save the file.
Restart the DigiCert ONE Clients app.
Note
Note:
The
.digicert-ucpcfolder is hidden by default. If you can’t find it, enable the option to show hidden files and folders in your operating system.Changes to config.json don’t take effect until DigiCert ONE Clients is restarted.
DigiCert ONE Clients version 1.9.0 uses your default OS browser.
To restore the default settings:
Delete the config.json file:
[Your HOME]\.digicert-ucpc\config.json
Restart the DigiCert ONE Clients app.
When DigiCert ONE Clients automatically uses the in-app browser
DigiCert ONE Clients automatically opens the in-app browser in the following situations.
When your sign-in method uses client certificate authentication
If your sign-in method uses client certificate authentication, DigiCert ONE Clients completes the sign-in process in the in-app browser.
Even if sign-in starts in your default browser, DigiCert ONE Clients must establish its own authenticated session when you return to the application. Using the in-app browser provides a consistent sign-in experience and prevents you from being prompted to authenticate with your client certificate multiple times.
When you're using older Software Trust Manager client tools
DigiCert ONE Clients uses the in-app browser when you're using a version of a Software Trust Manager client tool that doesn't support OAuth.
The following versions use the in-app browser:
Client tool | Version |
|---|---|
SMCTL | Earlier than |
PKCS11 | Earlier than |
KSP | Earlier than |
CSP | Earlier than |
Smartcard daemon (SCD) | Earlier than |
OpenSSL provider | Earlier than |
Notation plugin | Earlier than |
DigiCert ONE Clients detects whether the installed version of the client tool supports OAuth and switches browsers automatically. No manual configuration is required.
Known issue: Sign-in page stopped loading in Microsoft Edge
In rare cases, when Microsoft Edge is your operating system's default browser, the DigiCert ONE sign-in page may stop loading before sign in is complete.
To complete the sign-in process
Refresh the DigiCert ONE sign-in page in Microsoft Edge.
If the sign-in page still does not load, choose one of the following options:
Set another browser, such as Google Chrome, as your operating system's default browser, and then restart the sign-in process from DigiCert ONE Clients.
Configure DigiCert ONE Clients to use the in-app browser. See Switch to in-app browser.
Sign in to DigiCert ONE.