• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

API key rotation with zero downtime

Fatima Al-Rashid

From a governance perspective, we are required to rotate API credentials every 90 days per our information security policy. It is worth noting that we currently have seven production integrations consuming the FieldPulse API, including our customer portal, billing reconciliation service, and two vendor data feeds.

I have confirmed that the API key management interface supports only a single active key per account. When generating a new key, the previous key is immediately invalidated. This presents a significant operational risk: any credential rotation will result in service interruption until all seven integration points are updated and redeployed.

I am seeking clarification on the following points:

  1. Does FieldPulse support multiple concurrent API keys, or is there a mechanism to stage a new key before invalidating the existing one?
  2. If not, what is the recommended approach for credential rotation in high-availability environments?
  3. Are there plans to implement scoped API keys with independent lifecycle management?

Our current workaround involves scheduling rotation during a maintenance window, but this does not satisfy our continuous availability requirements. I would appreciate any guidance on how other organizations have addressed this constraint.

Parents
  • 0

    Thank you for the detailed guidance. The dual account strategy is viable for our use case, though it does introduce meaningful overhead in account management and webhook reconfiguration.

    It is worth noting that we will require formal documentation of the scoped key roadmap item for our audit trail. Is there a public issue or RFC I may reference?

    Additionally, I would request that the product team consider implementing a staged key deprecation mechanism — e.g., a 24-hour overlap period during which both keys are valid — as an interim measure prior to full scoped key support. This would satisfy our security requirements without the operational complexity of account duplication.

Reply
  • 0

    Thank you for the detailed guidance. The dual account strategy is viable for our use case, though it does introduce meaningful overhead in account management and webhook reconfiguration.

    It is worth noting that we will require formal documentation of the scoped key roadmap item for our audit trail. Is there a public issue or RFC I may reference?

    Additionally, I would request that the product team consider implementing a staged key deprecation mechanism — e.g., a 24-hour overlap period during which both keys are valid — as an interim measure prior to full scoped key support. This would satisfy our security requirements without the operational complexity of account duplication.

Children
No Data