Configuration

All configuration goes through IamClientBuilder. This page is the complete reference for the builder
options, their defaults, and validation.

The builder

Obtain it from IamClient::builder(), set options fluently, and finish with build() (async) or
build_blocking() (the blocking feature):

use std::time::Duration;
use laravel_iam::IamClient;

let iam = IamClient::builder()
    .base_url("https://iam.example.com/api/iam/v1")
    .token("svc_token")
    .timeout(Duration::from_secs(2))
    .issuer("https://iam.example.com")
    .audience("warehouse-api")
    .build()?;

Options

Validation

build() / build_blocking() validate the configuration (finish() in config.rs):

• base_url is required and non-empty. Missing or empty → IamError::Config.
• The trailing / is trimmed, so …/v1 and …/v1/ behave identically.
• The HTTP client is constructed with the timeout; a failure to build it is IamError::Network.

// Missing base_url is a configuration error, surfaced at build time.
let err = IamClient::builder().token("t").build();
assert!(matches!(err, Err(laravel_iam::IamError::Config(_))));

When issuer/audience are required

• check() and list_resources() do not need issuer/audience.
• verify_token() requires both. Calling it on a client built without them returns
  IamError::Config — see JWT / JWKS verification.

Environment-driven setup

A typical production wiring reads everything from the environment:

use std::time::Duration;
use laravel_iam::IamClient;

fn build_iam() -> Result<IamClient, Box<dyn std::error::Error>> {
    Ok(IamClient::builder()
        .base_url(std::env::var("IAM_BASE_URL")?)
        .token(std::env::var("IAM_SERVICE_TOKEN")?)
        .issuer(std::env::var("IAM_ISSUER")?)
        .audience(std::env::var("IAM_AUDIENCE")?)
        .timeout(Duration::from_millis(
            std::env::var("IAM_TIMEOUT_MS").ok()
                .and_then(|s| s.parse().ok())
                .unwrap_or(2000),
        ))
        .build()?)
}

Cargo features

See Installation for the dependency snippet and The blocking client.

Defaults at a glance

See also: Best practices: integration, Troubleshooting.