[OPENAM-13750] HTTP 500 error when trying v3.1 /sessions in API explorer Created: 11/Oct/18 Updated: 25/Jul/19 Resolved: 02/Nov/18 |
|
Status: | Resolved |
Project: | OpenAM |
Component/s: | rest |
Affects Version/s: | 6.5.0 |
Fix Version/s: | 6.5.0, 6.0.1, 5.5.2 |
Type: | Bug | Priority: | Major |
Reporter: | Mark Craig | Assignee: | Kajetan Hemzaczek |
Resolution: | Fixed | Votes: | 0 |
Labels: | AME, Must-Fix | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
ForgeRock Access Management 6.5.0-SNAPSHOT Build 3097c3a4f4 (2018-October-08 08:36) |
Attachments: |
![]() |
||||||||
Issue Links: |
|
||||||||
Target Version/s: | |||||||||
Rank: | 1|hzwx27: | ||||||||
Needs backport: |
Yes
|
||||||||
Verified Version/s: | |||||||||
Functional tests: |
No
|
Description |
Bug descriptionWhen trying these endpoints in the API explorer under http://openam.example.com:8080/openam/XUI/#api/explorer/sessions:
with _queryFilter=true, I get HTTP 500 errors. For example: How to reproduce the issue
Expected behaviourSuccessful response listing open sessions. Current behaviourHTTP 500 errors. It appears that the request URL is missing the realm in the root, e.g. /json/realms/root/sessions. |
Comments |
Comment by Andrew Vinall [ 12/Oct/18 ] |
Bug Triage: The Must-Fix element of this is to make sure that the problem is not backend. |
Comment by Kajetan Hemzaczek [ 16/Oct/18 ] |
This is backend problem. Also v2.1 is affected. |
Comment by Adam Heath [ 02/Nov/18 ] |
Reopening to mark that this should be backported and add target versions - this also affects (at least) AM version 6.0.0 |
Comment by Ľubomír Mlích [ 25/Jul/19 ] |
verified as fixed in AM 5.5.2-M6, there is no HTTP 500 comparing to AM 5.5.1 |