[MGRENTITLE-27] (evrk env) Cannot add or remove app entitlement using Kong baseUrl due to validation error Created: 30/Jan/24  Updated: 30/Jan/24  Resolved: 30/Jan/24

Status: Closed
Project: mgr-tenant-entitlements
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Yauhen Viazau Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: back-end, epam-eureka
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified
Environment:

"evrk"


Attachments: File EVRK_cannot_entitle_app.mp4     PNG File image-2024-01-30-12-34-14-118.png     PNG File image-2024-01-30-12-34-54-230.png     PNG File image-2024-01-30-12-35-35-700.png    
Issue links:
Cloners
is cloned by MGRENTITLE-28 (evrk env) No route for "/entitlement... In Review
Relates
relates to MGRENTITLE-6 PLACEHOLDER - mgr-tenant-entitlements... In Review
Sprint:
Development Team: None
RCA Group: TBD

 Description   

Overview: Cannot add or remove app entitlement using Kong baseUrl due to validation error

Steps to Reproduce:

  1. Add new app entitlement for any tenant:
    1. POST <kong URL>/entitlements
    2. Body (example):
      1. {     "tenantId": "<tenant UUID>",     "applications": [         "app-platform-minimal-0.0.7"     ] }
  2. Remove added app entitlement from the same tenant:
    1. DELETE <kong URL>/entitlements
    2. Body: the same as in Step 1

Expected Results: 

Step 1: Response with 201 status and body containing data on added entitlement

Step 2: Response with 200 status and body containing data on removed entitlement

Actual Results:

Step 1: Response with 400 status and body containing error message

Specific failing step:

Step 2: Response with 400 status and body containing error message:

Additional Information:

  • See attached screencast: EVRK_cannot_entitle_app.mp4
  • NOT reproduced using tenant-entitlement baseUrl initially (but reproduced using this baseUrl after entitlement fails with Kong baseUrl)

Interested parties:



 Comments   
Comment by Yauhen Viazau [ 30/Jan/24 ]

Closing this ticket as the issue is no longer reproducible when using proper authorization. I was only using authorization token but should have also used authorization header

Generated at Thu Feb 08 22:18:32 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.