Some endpoints require credentials. Fajita stores supported monitor secrets encrypted and uses them only for server-side checks.
How secrets are handled
- Fajita encrypts supported monitor secrets at rest and limits decryption to authorized server-side monitoring operations.
- After you save a secret, its value is masked in the interface. You can replace it, not read it back.
- Manual tests use the stored secret so a test reflects real behavior.
Header rules
- You set an authorization header with your token.
- Certain protocol headers are managed by Fajita and cannot be overridden.
- On a redirect to a different origin, authorization headers are not forwarded.
Rotation
Rotate a credential by replacing the stored secret. The next check uses the new value. Old values are not retained in check history.