Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: test Flipper feature flag in ApplicationController #21160

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ojbucao
Copy link
Contributor

@ojbucao ojbucao commented Mar 7, 2025

This PR ensures that all routes in the Accredited Representative Portal are properly gated behind the :accredited_representative_portal_pilot feature flag. If the flag is disabled, the API will immediately return 403 Forbidden, regardless of authentication.

@va-vfs-bot va-vfs-bot temporarily deployed to art/poa-requests/spec-feature-flag/main/main March 7, 2025 18:45 Inactive
@ojbucao ojbucao force-pushed the art/poa-requests/spec-feature-flag branch from 0b2a207 to 9a2ec9f Compare March 7, 2025 18:46
@ojbucao ojbucao changed the title feat: enforce Flipper feature flag in ApplicationController feat: test Flipper feature flag in ApplicationController Mar 7, 2025
•Added Flipper validation to ApplicationController spec to ensure API access is blocked when :accredited_representative_portal_pilot is disabled.
•Modified tests to check that the feature flag takes priority over authentication.
•Ensured existing authentication tests remain intact, validating correct behavior when the flag is enabled.
•If Flipper is disabled, requests now return 403 Forbidden before checking tokens or audience validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants