Skip to main content
The starter is configured with Spring Boot properties under the nexus.* prefix.

Property reference

Durations take the standard Spring Boot forms - 60s, 500ms, 5m, PT60S.

Beans the auto-configuration picks up

NexusConfig - the plain Java client

Outside Spring, or in a NexusClient bean of your own, the same settings go through NexusConfig.builder(): null always means the default; a value that cannot be meant is rejected with a NexusConfigException whose option() names it.

API key types

Calling getSecret(...) with a public key throws NexusPublicKeyException without a network call.

Where to keep the API key

Anywhere Spring Boot already reads configuration from - environment variables, a secret store mounted as properties, your pipeline:
Combined with profile-based config:
The SDK never logs the key; its log lines carry the key type only.

The active profile cannot come from Nexus

SPRING_PROFILES_ACTIVE (spring.profiles.active) is read while the Environment is prepared, before any bean - the NexusClient included - exists. Nexus values are read through the client and are not a Spring PropertySource, so a profile, and anything else Spring reads at startup, has to come from the environment, the command line or application*.yml.

Choosing the TTL

With the stream connected, changes arrive within milliseconds regardless of the TTL, and the background refresh then runs no more often than once a minute. The TTL is the safety net for the time the stream is not connected.

Disabling the stream

Useful where outbound long-lived connections are blocked (some serverless platforms, certain corporate proxies).

A client bean of your own

For settings the properties do not cover - for example an HttpClient that goes through a corporate proxy - register your own NexusClient bean; the auto-configuration backs off:
A client of your own gets no logger unless you pass one: .logger(new Slf4jNexusLogger()) keeps the starter’s logging.