4.5.0

This minor release addresses the following items:

Security fixes

• ml-app-deployer no longer defaults to a username of "admin" and a password of "admin" when connecting to MarkLogic. Most users will not be impacted, particularly ml-gradle users that are already setting at least mlUsername and mlPassword. You will only be impacted if you are embedding ml-app-deployer, not configuring any authentication, and assuming that "admin/admin" should authenticate successfully.

Deprecations

• Connections to the MarkLogic Manage API and Admin API are now made with OkHttp instead of Apache HTTP. This was done to allow for the connection plumbing in the MarkLogic Java Client to be reused.
• As a result, a small number of methods that depend on Apache HTTP APIs in the com.marklogic.rest.util have been deprecated and will be removed in the next major release. These methods will all continue to work - e.g. you can continue to use RestTemplateUtil with the Apache HTTP-specific APIs - but they are no longer used by the rest of the ml-app-deployer library when making connections to MarkLogic.

New features

• Now supports SAML, Kerberos, and Certificate authentication for all connections to MarkLogic . New properties to support these connection types can be found in the ml-gradle Property Reference.
• Supports connections for the upcoming MarkLogic Cloud release.
• Depends on ml-javaclient-util 4.5.0 and Java Client 6.1.0