Centralized Client ID / Secret Management for Integrations (Admin Only)

Customers need a way to centrally manage integration credentials (Client IDs and Client Secrets). Today, when a credential such as an Azure Client Secret is rotated, it must be manually updated in every integration where it is used. This becomes difficult when the same Azure application is used across multiple integrations, as there is currently no easy way to identify which integrations share the same Client ID.

Proposed Enhancement:

Add a centralized credential management section within the Company Settings page of the platform.

Location:

https://app.halosecurity.com/user/account/company/

This new section would allow administrators to securely store and manage Client IDs and Client Secrets used by integrations.

When configuring or editing integrations, users would be able to select an existing credential from this centralized list instead of manually entering the Client ID and secret each time.

Access Control:

• This section should only be visible within the Company Settings page.

• Access should be restricted to Admin users only.

• Client Secrets should remain masked/encrypted in the UI.

Key Benefits:

• Simplifies credential rotation (e.g., Azure client secret rotation).

• Eliminates the need to manually update credentials across multiple integrations.

• Reduces configuration errors when secrets are rotated.

• Provides visibility into which credentials are being reused.

Additional Suggested Capability:

Provide a simple export or table view showing:

• Integration Name

• Associated Client ID

This would allow administrators to quickly identify which integrations rely on a specific Azure application when credentials are rotated.

Example Use Case:

A customer recently rotated a secret on an Azure application used across 15 integrations. Because the platform does not show Client IDs in a centralized way or allow credential reuse, the team had to manually open and update each integration individually. A centralized credential store would allow the secret to be updated once and automatically applied to all integrations using that credential.