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.

Sign up for GitHub

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

Jump to bottom

CE API User Management #1658

Open
wants to merge 27 commits into
base: main
Choose a base branch
from
Open

CE API User Management #1658

wants to merge 27 commits into from

Conversation

youfoundmanesh
Copy link
Contributor

  • Add Pre File Fetch Sensitivity Check

  • Verify user and veteran sensitivity levels are compatible.

  • Add specs and supporting services needed to perform sensitivity level checks.

  • Implement Banner for Unauthorized Vet Access

  • Restore Old Error Message Logic

Resolves #{efolder issue number} / department-of-veterans-affairs/caseflow#{caseflow issue number} / CASEFLOW-{JIRA number}

Description

Please explain the changes you made here.

Acceptance Criteria

  • Code compiles correctly

Testing Plan

  1. Go to ...

User Facing Changes

  • Screenshots of UI changes added to PR & Original Issue
BEFORE AFTER

Code Documentation Updates

  • Add or update code comments at the top of the class, module, and/or component.

Database Changes

Only for Schema Changes

  • Timestamps (created_at, updated_at) for new tables
  • Column comments updated
  • Verify that migrate:rollback works as desired (change supported functions)
  • Query profiling performed (eyeball Rails log, check bullet and fasterer output)
  • Appropriate indexes added (especially for foreign keys, polymorphic columns, unique constraints, and Rails scopes)
  • Add your indexes safely (see Caseflow::Migrations
  • DB schema docs updated with make docs (after running make migrate)
  • #appeals-schema notified with summary and link to this PR
  • Any non-obvious semantics or logic useful for interpreting database data is documented at Caseflow Data Model and Dictionary

Integrations: Adding endpoints for external APIs

  • Check that Caseflow's external API code for the endpoint matches the code in the relevant integration repo
    • Request: Service name, method name, input field names
    • Response: Check expected data structure
  • Update Fakes
  • Integrations impacting functionality are tested in Caseflow UAT

tradesmanhelix and others added 27 commits October 8, 2024 15:04
@tradesmanhelix @youfoundmanesh
Add Pre File Fetch Sensitivity Check (#1652)
5b3c218 
* Add Pre File Fetch Sensitivity Check

- Verify user and veteran sensitivity levels are compatible.

- Add specs and supporting services needed to perform sensitivity
level checks.

* Implement Banner for Unauthorized Vet Access

* Restore Old Error Message Logic
@tradesmanhelix @youfoundmanesh
Add Specs to Cover Additional Sensitivity Cases (#1662)
d9a2f77
@tradesmanhelix @youfoundmanesh
Gate VBMS Methods with Sensitivity Checks (#1665)
9557efd 
* Gate VBMS Methods with Sensitivity Checks

Validate user access to veteran before allowing fetch of veteran
data.

* Remove Unneeded allow Directives in Spec
@tradesmanhelix @youfoundmanesh
Remove Unneeded Sensitivity Checks (#1666)
f1d396f 
* Remove Unneeded Sensitivity Checks

Checks are already handled by the sensitive_record method.

* Fix Non-Forbidden Banner Styling
@tradesmanhelix @youfoundmanesh
Restore Pre-Fetch Sensitivity Check Logic & Add Frontend Feature Togg…
af9d251 
…le (#1667)

* Pass Sensitivity Check Feature Toggle to UI

* Restore Manifest Sensitivity Logic
@youfoundmanesh
Updated ruby_claim_evidence_api gem
e9fd8ab
@tradesmanhelix @youfoundmanesh
Fix Missing Manifest User Causing Sensitivity Check Failures (#1675)
01576e4 
* Fix User Missing for BGS Sensitivity Check

- Update the manifests_controller's refresh method to use the
  find_or_create_by_user method to find a manifest. This will
  ensure that the user is set correctly for BGS calls.

- Move SensitivityLevelCheckFailure logic to the base_controller.

* Fix Misc. Issues

- Move rescue_from for BGS errors into the API V1 controller so
  its existing standard error rescue doesn't catch this exception.

- Improve manifests_controller request spec with sensitivity check
  logic.
@tradesmanhelix @cacevesva @youfoundmanesh
Use New Sensitivity Check Method (#1676)
2f41563 
- Use new method to check user/veteran sensitivity compatibility
  in the V2 ApplicationController.

- This will prevent the old "use BGS error to verify access" logic
  from running.

Co-authored-by: cacevesva <[email protected]>
@tradesmanhelix @youfoundmanesh
Update Specs to Address Failures (#1677)
183286b
@tradesmanhelix @youfoundmanesh
Send Veteran Number in Restart Request (#1679)
c3d84ce 
* Send Veteran Number in Restart Request

* Update Link rel Param
@tradesmanhelix @youfoundmanesh
Update CE API Gem (#1680)
1a22df9
@tradesmanhelix @youfoundmanesh
Update Logic for Setting Veteran ID in Request (#1681)
0555acf 
- Remove recently-added frontend logic for setting veteran ID in
  refresh request as it is unreliable in the way it sets the
  veteran ID.

- Update manifests_controller to set the veteran ID using the
  manifest as this is much more reliable.
@tradesmanhelix @youfoundmanesh
Update JSON Parsing Logic to Handle CE API Gem Changes (#1686)
cb43002 
- Gem now returns the JSON body of a HTTP response, so our
  response parsing code needed to be updated to handle the new
  format.

- Update the VBMS service to alert us of any API responses that
  can't be parsed so we can troubleshoot them.
@youfoundmanesh
Updated ruby_claim_evidence_api
4a4f847
@tradesmanhelix @youfoundmanesh
Add current_user to SaveFilesInS3 Job (#1688)
9e2a9a4 
- Since the SaveFilesInS3 job is spawned by another job, it does
  not have access to RequestStore[:current_user] which is needed
  for verifying veteran/user sensitivity compatibility.

- This PR also fixes several Rubocop violations in various files.
@SanthiParakal133 @youfoundmanesh
add check for empty result (#1687)
6d18455
@tradesmanhelix @youfoundmanesh
Add Script for Finding Valid UAT Testing Users (#1690)
1eaf33c
@Kevma50287 @youfoundmanesh
Kev ma/appeals 58216 time adjust (#1692)
9322a50 
* Adjusted UI_EXPIRY_HOURS based on deploy environment

* Adjust API HOURS
@tradesmanhelix @youfoundmanesh
Fix Incorrect Keyword in Script (#1693)
89a91f0
@tradesmanhelix @youfoundmanesh
Handle All Possible Errors in Script (#1694)
455fef7
@tradesmanhelix @youfoundmanesh
Improve Script Output (#1695)
ae2f385 
- Sort output by sensitivity level.

- Display total result count for each level.
@youfoundmanesh
Updated ruby_claim_evidence_api gem with ref
8b83f87
@youfoundmanesh
Update feature toogle to send_current_user_cred
c13cb12
@youfoundmanesh
Update feature toogle to send_current_user_cred_to_ce_api
b701318
@Kevma50287 @youfoundmanesh
Kev ma/appeals 59461 (#1701)
919352c 
* Removed send_user feature flag, combined with use_ce_api

* Updated vbms service spec

* Updated manifest spec for uat expiration hours

* send user feature toggle combined with use_ce_api

* Combined with ce_api feature toggle

* Update failing rspecs

* Remove feature flag from method, wrapped method with all ce api calls

* wrap ce_api related sensitivity changes

* Fix failing specs, reverted to prior code outside of feature flag

* update manifest expiry hours to not change in test + non prod

* remove pry, reverted to previous test case

* If user is blank, return

* update front end error handling

* Linting

* Revert changes
@Kevma50287 @youfoundmanesh
typo fix (#1702)
50d2d0c
@Kevma50287 @youfoundmanesh
Kev ma/appeals 58827 v2 (#1703)
05044a2 
* Change type_description to mapping

* Updated rspecs to handle edge case
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@youfoundmanesh @tradesmanhelix @SanthiParakal133 @Kevma50287