Remove Okta monitor beta flag

[jpople]

Ticket ENG-2625

Description Of Changes

Removes beta flag for Okta monitors, Okta is now available by default

Steps to Confirm

0. Verify Okta monitor beta flag is no longer present
1. Create an Okta integration and monitor
2. Run the monitor
3. View the results
4. Should be able to use all Okta-related functionality.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 11, 2026 5:50pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 11, 2026 5:50pm

[greptile-apps]

Greptile Overview

Greptile Summary

Removed the oktaMonitor beta flag to make Okta integration and monitoring functionality available by default in all environments.

Key changes:

• Removed oktaMonitor flag definition from flags.json
• Removed conditional logic gating infrastructure monitor type behind the flag in MonitorList.tsx
• Removed conditional filtering of identity provider category and Okta integration type in SelectIntegrationType.tsx
• Removed identity provider tab filtering in useIntegrationFilterTabs.tsx
• Removed test flag override in config-wizard.cy.ts

The change cleanly enables Okta functionality across the application. One minor style issue with an extra blank line remains.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a straightforward feature flag removal that makes Okta functionality available by default. All references to the flag have been properly removed across the codebase, including the flag definition, conditional logic, filtering, and test overrides. The changes are clean, consistent, and follow the expected pattern for feature flag removal.
• No files require special attention

Important Files Changed

Filename	Overview
clients/admin-ui/src/flags.json	Removed oktaMonitor beta flag definition completely
clients/admin-ui/src/features/data-discovery-and-detection/action-center/MonitorList.tsx	Removed flag check, infrastructure monitor now always available
clients/admin-ui/src/features/integrations/add-integration/SelectIntegrationType.tsx	Removed flag checks and Okta filtering, has extra blank line

[greptile-apps]

_{5 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

extra blank line left after removing flag-based filtering

Suggested change

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[gilluminate]

tested locally, looks good!