[OPENAM-12166] Resource #3.0 logoutByHandle request fail with status 500 error Created: 01/Dec/17  Updated: 02/Sep/19  Resolved: 29/Mar/18

Status: Resolved
Project: OpenAM
Component/s: API descriptor
Affects Version/s: 14.5.0, 14.5.1
Fix Version/s: 6.0.0, 5.5.2

Type: Bug Priority: Major
Reporter: Aaron Haskins Assignee: Dipu Seminlal
Resolution: Fixed Votes: 0
Labels: AME, Must-Fix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 25852_Exceptions.txt    
Target Version/s:
Needs backport:
Yes
Support Ticket IDs:
Verified Version/s:
Needs QA verification:
Yes
Functional tests:
No
Are the reproduction steps defined?:
Yes and I used the same an in the description

 Description   

Bug description

Requests to logoutByHandle using API Version Resource 3.0 fails with a 500 error. Different exceptions are returned by 5.5.1 than are returned by 5.5.0. 5.5.1 also returns different exceptions depending on whether one or more session handles are passed in to the request.

How to reproduce the issue

Details steps outlining how to recreate the issue (remove this text)

  1. Create a couple of sessions with demo user
  2. Find their shandle values (example shown here)
  3. In the API explorer, under resource 3.0 (Session v3.0), send a request to /sessions#3.0_action_logoutbyhandle adding the shandle(s) to the requestPayload (alternatively, use a curl request). If using one shandle, try removing the brackets, you'll see a different exception thrown.
Expected behaviour
{
  "result": {
    "shandle:AQIC5w...NDcx*": true,
    "shandle:AQIC5w...MTY3*": true
  }
}
Current behaviour
500 error returned

Work around

Use API Version Resource 2.0



 Comments   
Comment by Ľubomír Mlích [ 02/Sep/19 ]

Reproduced in ForgeRock Access Management 5.5.1 Build 96b47ad4f1 (2017-October-26 15:41), I can see HTTP 500

Verified as fixed in ForgeRock Access Management 5.5.2-M7 Build 965200a558 (2019-August-20 08:11), there is HTTP 200 as expected

 

Generated at Sat Nov 28 11:15:07 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.