Skip to main content

Using MarkLogic Content Pump (mlcp)

Invoking mlcp

Once you configure your XDBC App Server and user for Kerberos external security, then you can do the following to use Kerberos authentication with mlcp:

  • Use kinit or a similar program on your mlcp client host to create and cache a Kerberos Ticket to Get Tickets (TGT) for a principal you assigned to a MarkLogic user.

  • Invoke mlcp with no -username and no -password option from the environment in which you cached the TGT.

For example, suppose you configured an XDBC App Server on port 9010 of host “ml-host” to use “kerberos-ticket” authentication. Further, suppose you associated the Kerberos principal name “kuser” with the user “mluser”. Then the following commands result in mlcp authenticating with Kerberos as user “kuser” and importing documents into the database as “mluser”.

kinit kuser
...
mlcp.sh import -host ml-host -port 9010 -input_file_path src_dir

You do not necessarily need to run kinit every time you invoke mlcp. The cached TGT typically has a lifetime over which it is valid.

In this section: