b2c-config

# B2C Config Skill

Use the `b2c setup config` command to view the resolved configuration and understand where each value comes from. This is essential for debugging configuration issues and verifying that the CLI is using the correct settings.

> **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli setup config`).

## When to Use

Use `b2c setup config` when you need to:

- Verify which configuration file is being used
- Check if environment variables are being read correctly
- Debug authentication failures by confirming credentials are loaded
- Understand credential source priority (dw.json vs env vars vs plugins)
- Identify hostname mismatch protection issues
- Verify MRT API key is loaded from ~/.mobify

## Examples

### View Current Configuration

```bash
# Display resolved configuration (sensitive values masked by default)
b2c setup config

# View configuration for a specific instance from dw.json
b2c setup config -i staging

# View configuration with a specific config file
b2c setup config --config /path/to/dw.json
```

### Debug Sensitive Values

```bash
# Show actual passwords, secrets, and API keys (use with caution)
b2c setup config --unmask
```

### JSON Output for Scripting

```bash
# Output as JSON for parsing in scripts
b2c setup config --json

# Pretty-print with jq
b2c setup config --json | jq '.config'

# Check which sources are loaded
b2c setup config --json | jq '.sources'
```

## Understanding the Output

The command displays configuration organized by category:

- **Instance**: hostname, webdavHostname, codeVersion
- **Authentication (Basic)**: username, password (for WebDAV)
- **Authentication (OAuth)**: clientId, clientSecret, scopes, authMethods
- **TLS/mTLS**: certificate, certificatePassphrase, selfSigned (for two-factor auth)
- **SCAPI**: shortCode
- **Managed Runtime (MRT)**: mrtProject, mrtEnvironment, mrtApiKey
- **Metadata**: instanceName (from multi-instance configs)
- **S