fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
110 lines
3.0 KiB
Markdown
110 lines
3.0 KiB
Markdown
# Cloudflare Credentials Updated
|
|
|
|
**Last Updated:** 2026-01-31
|
|
**Document Version:** 1.0
|
|
**Status:** Active Documentation
|
|
|
|
---
|
|
|
|
**Date:** 2025-01-20
|
|
**Status:** ✅ Credentials Updated
|
|
**Purpose:** Document Cloudflare credentials update
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
Cloudflare credentials have been updated in the `.env` file with the provided values.
|
|
|
|
---
|
|
|
|
## Updated Credentials
|
|
|
|
### Global API Key
|
|
- **Variable:** `CLOUDFLARE_API_KEY`
|
|
- **Value:** `65d8f07ebb3f0454fdc4e854b6ada13fba0f0`
|
|
- **Status:** ✅ Updated in `.env`
|
|
- **Note:** This is the legacy API key method. Consider migrating to API Token for better security.
|
|
|
|
### Origin CA Key
|
|
- **Variable:** `CLOUDFLARE_ORIGIN_CA_KEY`
|
|
- **Value:** `v1.0-e7109fbbe03bfeb201570275-231a7ddf5c59799f68b0a0a73a3e17d72177325bb60e4b2c295896f9fe9c296dc32a5881a7d23859934d508b4f41f1d86408e103012b44b0b057bb857b0168554be4dc215923c043bd`
|
|
- **Status:** ✅ Updated in `.env`
|
|
- **Purpose:** Used for Cloudflare Origin CA certificates
|
|
|
|
---
|
|
|
|
## Current Configuration
|
|
|
|
The `.env` file now contains:
|
|
```bash
|
|
CLOUDFLARE_API_KEY="65d8f07ebb3f0454fdc4e854b6ada13fba0f0"
|
|
CLOUDFLARE_ORIGIN_CA_KEY="v1.0-e7109fbbe03bfeb201570275-231a7ddf5c59799f68b0a0a73a3e17d72177325bb60e4b2c295896f9fe9c296dc32a5881a7d23859934d508b4f41f1d86408e103012b44b0b057bb857b0168554be4dc215923c043bd"
|
|
```
|
|
|
|
---
|
|
|
|
## Security Recommendations
|
|
|
|
### 1. Migrate to API Token (Recommended)
|
|
|
|
While the Global API Key is functional, Cloudflare recommends using API Tokens for better security:
|
|
|
|
**Benefits of API Tokens:**
|
|
- ✅ More secure (limited scopes)
|
|
- ✅ Can be revoked individually
|
|
- ✅ Better audit trail
|
|
- ✅ Recommended by Cloudflare
|
|
|
|
**Migration Steps:**
|
|
1. Create API Token at: https://dash.cloudflare.com/profile/api-tokens
|
|
2. Use "Edit zone DNS" template OR create custom token with:
|
|
- **Zone** → **DNS** → **Edit**
|
|
- **Account** → **Cloudflare Tunnel** → **Edit**
|
|
3. Add to `.env`: `CLOUDFLARE_API_TOKEN="your-token"`
|
|
4. Update scripts to use `CLOUDFLARE_API_TOKEN`
|
|
5. Keep `CLOUDFLARE_API_KEY` temporarily for backwards compatibility
|
|
6. Remove `CLOUDFLARE_API_KEY` after verification
|
|
|
|
**See:** [SECRETS_KEYS_CONFIGURATION.md](SECRETS_KEYS_CONFIGURATION.md) (Phase 4)
|
|
|
|
---
|
|
|
|
## Verification
|
|
|
|
### Verify Credentials Are Set
|
|
|
|
```bash
|
|
# Check .env file
|
|
grep -E "CLOUDFLARE_API_KEY|CLOUDFLARE_ORIGIN_CA_KEY" .env
|
|
|
|
# Test API Key (if needed)
|
|
curl -X GET "https://api.cloudflare.com/client/v4/user" \
|
|
-H "X-Auth-Email: your-email@example.com" \
|
|
-H "X-Auth-Key: 65d8f07ebb3f0454fdc4e854b6ada13fba0f0" \
|
|
-H "Content-Type: application/json"
|
|
```
|
|
|
|
---
|
|
|
|
## Related Documentation
|
|
|
|
- [Secrets and Keys Configuration](./SECRETS_KEYS_CONFIGURATION.md)
|
|
- [Required Secrets Inventory](REQUIRED_SECRETS_INVENTORY.md)
|
|
- [Cloudflare API Setup](CLOUDFLARE_API_SETUP.md)
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
1. ✅ Credentials updated in `.env`
|
|
2. ⏳ Consider migrating to API Token (recommended)
|
|
3. ⏳ Test API operations with updated credentials
|
|
4. ⏳ Update scripts if needed
|
|
|
|
---
|
|
|
|
**Last Updated:** 2025-01-20
|
|
**Status:** ✅ Credentials Updated
|
|
**Next Review:** After API Token migration (if applicable)
|