Authentication and credentials
Configure how sdmx-dl authenticates against protected data sources — credentials are configured once, in a source config file shared by every flavor.
sdmxdl.driver.authScheme=BASIC
For OAuth2/Msal-backed sources, the same source configuration can also define:
sdmxdl.authenticator.clientId=...
sdmxdl.authenticator.authority=...
sdmxdl.authenticator.scopes=...
The CLI reads the same source configuration file, so the same authentication properties apply when running commands such as:
sdmx-dl fetch data ECB EXR M.CHF.EUR.SP00.A --sources sources.csv
The web service uses the same source configuration model.
When a protected source is accessed through REST or gRPC, the credential flow is triggered on first use and secrets are stored in the native OS keystore when available.
curl "localhost:4559/sdmx-dl/v2/ECB/EXR/data?key=M.CHF.EUR.SP00.A"
grpcurl -d '{"source":"ECB","flow":"EXR","key":"M.CHF.EUR.SP00.A"}' -plaintext localhost:4557 sdmxdl.grpc.v2.SdmxWebManager.GetData
- Authentication is configuration, not code: the same
sdmxdl.driver.authScheme/sdmxdl.authenticator.*properties apply whether the source config is read by the Java library, the CLI, or the web service. - See Authentication for the full list of supported schemes (BASIC, MSAL) and their properties.
- Credentials/tokens are cached in the native OS keystore; the current implementation only supports Windows.