Issues fixed in MarkLogic Server 10.0-10.1

sjs referencing XQuery modules with the same name may use the wrong module

When multiple XQuery modules with the same filename, but different paths exist in the modules database, SJS modules that reference the XQuery modules using the require function may not retrieve the correct module relative to the calling module.

Server hangs when turning log encryption on when telemetry is enabled

MarkLogic will hang when switching log encryption on if telemetry is enabled with log level set to info and the keystore component logs a warning or error message while enabling log encryption.

MarkLogic connections to AWS KMS and Azure KeyVault fail due to the use of TLSv1.0

AWS and Azure have discontinued the use of TLS 1.0 and 1.1 and now require TLS 1.2. MarkLogic does not yet support TLS 1.2 for communication with an external KMS so once AWS and Azure require TLS 1.2, MarkLogic will no longer be able to communicate with AWS KMS or Azure Key Vault.

The "property" querystring parameter is not supported in the v2/forests REST API

The documentation https://docs.marklogic.com/REST/GET/manage/v2/forests/[id-or-name]@view=counts states that "property" is a querystring parameter that can be used to request specific properties but it does not work.