feat(lib): Updated error types

[dmihalcik-virtru]

• Untyped Error objects indicate a likely bug in the library itself
  • The messages should be prefixed internal:
  • Samples include bad resource management or missing values in fields that should be const.
• TdfError should be the root for all errors an application might theoretically screen for to find out if something is wrong in their application that might be caused by TDF or this library. Includes a novel code field to allow tracking based on a unique(?) error code
• ConfigurationError should be able to be fixed by updating the application code.
• InvalidFileError indicates that a file is likely tampered with or corrupt, although for some errors this may also indicate something is wrong with the user KAS. There are several subtypes when there may be changes to the configuration or user settings that could potentially fix the issue.
  • DecryptError may indicate that the key is incorrect; this could be caused by using a remote or CKS key is out of date, indicating a failure on the server side, but at the moment we have not implemented this.
  • IntegrityError indicates that the segment or global hash is incorrect. This could indicate a file was generated with a deprecated library that uses a different hash calculation.
  • UnsafeUrlError indicates that one or more required Key Access Objects refers to a remote KAS that is not in the allowlist. You can manually check the URL and add it to the allowlist in the client constructor if is a supported KAS.
• NetworkError indicates a network connectivity error (e.g. during rewrap or key lookup), or a 5xx error on a service
• UnauthenticatedError indicates that the Bearer token or a required DPoP was not attached to a request. This is often fixable with a mix of IdP/OAuth configuration changes and changes to the application or by adding custom middleware or some combination of all these.
• PermissionDeniedError indicates that a service (rewrap or public key) has denied access, either due to traditional login (bearer token insufficient scope is one possibility) or due to ABAC (client entity does not have sufficient attributes for policy)
• UnsupportedFeatureError indicates that an enum in the file or a KAS requirement is not met, e.g. KAS uses an unsupported EC curve, or the TDF file embeds such a curve; could indicate the file was generated with a newer, experimental, or deprecated/removed feature.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
40.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud