Hide CIRA Options in Create Profile When CIRA Is Disabled

[graikhel-intel]

Description

Console already exposes the server capabilities through: GET /api/v1/server/features

Response:

{
  "ciraEnabled": false
}

When ciraEnabled is false, both the UI and API should prevent users from configuring CIRA.

Currently, users can still see CIRA configuration options even though the server does not support CIRA, which adds unnecessary clutter and can be confusing. The backend should also reject requests that attempt to configure CIRA when the feature is disabled.

Areas to consider include:

• Hide the CIRA Configs navigation item.
• Hide the CIRA provisioning option in the Profile configuration page.
• Hide any other CIRA-specific UI that depends on the feature being enabled.
• Reject profile create/update requests that configure CIRA when ciraEnabled is false.

The UI should use the server feature response to determine whether CIRA functionality should be displayed, while the API should enforce the same restriction regardless of the client.

Acceptance Criteria

• When ciraEnabled is false, the CIRA Configs navigation item is hidden.
• When ciraEnabled is false, the CIRA provisioning option is hidden from the Profile configuration page.
• The API rejects profile create/update requests that enable or configure CIRA when ciraEnabled is false.
• Other CIRA-specific UI is hidden when the feature is disabled.
• Standard DoD