Resolved issues
This section lists previously reported issues that are resolved in Tungsten Token Vault 3.8.0.
| ID | Title | Description |
|---|---|---|
| 2081489 | Security vulnerability in the used System.Data.SqlClient library |
Token Vault used a version of System.Data.SqlClient library that was affected by the CVE-2024-0056 security vulnerability. |
| 2074443, 2074435 | Security vulnerability in the used Microsoft.IdentityModel.Tokens.Jwt library |
Token Vault used a version of Microsoft.IdentityModel.JsonWebTokens library that was affected by the CVE-2024-21319 security vulnerability. |
| 2074437, 2074434 | Security vulnerability in the used System.IdentityModel.Tokens.Jwt library |
Token Vault used a version of System.IdentityModel.Tokens.Jwt library that was affected by the CVE-2024-21319 security vulnerability. |
| 2072435 | Security vulnerability in the used Azure.Identity library |
Token Vault used a version of Azure.Identity library that was affected by the CVE-2023-36414 security vulnerability. |
| 2010822 | UI issue when configuring iManage Work Authorization provider with iManage Cloud |
The "Application Registration Request" button disappeared when one of the subdomains of cloudimanage.com was configure with the "Server URL" setting in the iManage Work Authorization Provider. |
| 1978072 | Certificate validation issue |
Token Vault could be configured with a certificate that had no private key, causing errors when performing the workflows configured with modern authentication. |
| 1947719 | Starting issue in certain cases |
In certain environments, Token Vault started in maintenance mode when the Active Directory type setting was configured as either "On-premises only" or "Microsoft Entra ID & On-premises." |