diff --git a/docs/en/security/images/nexus.png b/docs/en/security/images/nexus.png new file mode 100644 index 00000000000..7be7a6536f6 Binary files /dev/null and b/docs/en/security/images/nexus.png differ diff --git a/docs/en/security/tribe-clients-integrations/java.asciidoc b/docs/en/security/tribe-clients-integrations/java.asciidoc index ad36a569019..6921786af10 100644 --- a/docs/en/security/tribe-clients-integrations/java.asciidoc +++ b/docs/en/security/tribe-clients-integrations/java.asciidoc @@ -90,6 +90,40 @@ dependencies { -------------------------------------------------------------- -- +If you are using a repository manager such as [Nexus OSS](https://www.sonatype.com/nexus-repository-oss) within your +company, you need to add the repository as per the following screenshot: + ++ +image::images/nexus.png["Adding the Elastic repo in Nexus",link="images/nexus.png"] ++ + +Then in your project's `pom.xml` if using maven, add the following repositories and dependencies definitions: + +[source,xml] +-------------------------------------------------------------- + + + org.elasticsearch.client + x-pack-transport + {version} + + + + + + local-nexus + Elastic Local Nexus + http://0.0.0.0:8081/repository/elasticsearch/ + + true + + + false + + + +-------------------------------------------------------------- + . Set up the transport client. At a minimum, you must configure `xpack.security.user` to include the name and password of your transport client user in your requests. The following snippet configures the user credentials globally--every request