Configuration¶
Publish the package configuration when you want to inspect or customize it:
The package defaults to QoreID. Set IDENTITY_MADE_EASY_PROVIDER to change the default provider, or select a provider explicitly with Identity::driver('provider').
Environment variables¶
Set only the credentials for providers your application uses. Values below are examples, not real credentials.
| Variable | Purpose | Default |
|---|---|---|
IDENTITY_MADE_EASY_PROVIDER |
Default provider (qoreid, mono, or idenvault) |
qoreid |
QOREID_CLIENT_ID |
QoreID client ID | — |
QOREID_SECRET |
QoreID client secret | — |
QOREID_BASE_URL |
QoreID API origin | https://api.qoreid.com |
QOREID_HTTP_TIMEOUT |
QoreID HTTP timeout in seconds | 30 |
MONO_SECRET_KEY |
Mono server secret key | — |
MONO_WEBHOOK_SECRET |
Shared secret used to authenticate Mono webhooks | — |
MONO_BASE_URL |
Mono API origin | https://api.withmono.com |
MONO_HTTP_TIMEOUT |
Mono HTTP timeout in seconds | 30 |
IDENVAULT_API_KEY |
IdenVault API key | — |
IDENVAULT_BASE_URL |
IdenVault API base URL | https://idenvault.com/api/v1 |
IDENVAULT_HTTP_TIMEOUT |
IdenVault HTTP timeout in seconds | 30 |
IDENVAULT_WEBHOOK_SECRET |
HMAC secret used to authenticate IdenVault webhooks | — |
Example server-side environment configuration:
IDENTITY_MADE_EASY_PROVIDER=qoreid
QOREID_CLIENT_ID=your_qoreid_client_id
QOREID_SECRET=your_qoreid_secret
QOREID_BASE_URL=https://api.qoreid.com
QOREID_HTTP_TIMEOUT=30
Provider credentials are independent. Mono and IdenVault are opt-in and are not selected unless configured as the default or requested by name. Base URLs can point to approved provider test environments where supported; use the exact URL and credentials specified by the provider.
Secret handling¶
- Do not commit
.envfiles, API keys, client secrets, or webhook secrets. - Do not expose credentials or QoreID SDK session tokens in frontend build variables.
- Keep webhook secrets separate from outbound API credentials.
- Avoid logging identity request or response bodies; they can contain sensitive personal data.
- Use your deployment platform's secret manager for production values.
Laravel configuration is cached in production using php artisan config:cache. After changing environment variables, refresh the cached configuration as part of your deployment process.