01-05-2023 06:32 AM
Hi,
I am using the PSIRT APIs for a web application and it works great. However, some endpoints that support pagination are not having the paging object in their response body.
For example, Query by Year supports pageIndex and pageSize and I get the paging object in the response body in Postman. (See Query-by-Year.jpg attached image). But for Query by Product which supports pageIndex and pageSize, I don't get the paging object in the response body, and I am only limited to the first 100 results (See Query-by-Product.jpg attached image). Also, pageIndex and pageSize don't work for any of the OSType/{OSType} endpoints.
TL;DR
Pagination works only with Query by Year
Is that a bug? Who should I report this issue to?
Thank you
Osama Abbas
Solved! Go to Solution.
04-04-2023 08:34 PM
01-05-2023 03:47 PM
Hello Osama,
Looking at this. Will post an update shortly.
Thanks.
01-06-2023 01:24 PM
Hello Osama,
Pagination not implemented for all API. We have a dev engaged and we need to work and add pagination for the endpoints which its missing. Once identified all missing endpoints and a timeline to implement I will update the documentation for the OpenVuln API and update this thread.
For some of the endpoints whilst the pagination is working correctly we are not responding with the pagination Object. We will look to address this as well.
Thanks for bringing this to our attention.
01-23-2023 06:19 AM
Hi Poxman,
Any updates?
Thank you
01-23-2023 01:44 PM
Hello Omar,
Fix is scheduled to be deployed on 12th Feb 2023.
A review was conducted and the following endpoints will be updated; with the fixes:
Only endpoints that return multiple pages support pagination.
Thanks.
01-23-2023 01:56 PM
Sorry to correct you, but It's Osama, not Omar :).
Have a great day!
02-13-2023 08:10 AM - edited 02-14-2023 12:51 AM
Hi Oxman,
Since I noticed a change on the 12th of Feb on the following API endpoints:
I think the fix still needs some work to be done.
I'll take (1) as a reference with Cisco Identity Services Engine Software as an example. Yes the paging object does exist in the response now , but it has two issues:
"paging": {
"next": "/product?product=Cisco Identity Services Engine Software?pageIndex=13&pageSize=10",
"prev": "/product?product=Cisco Identity Services Engine Software?pageIndex=11&pageSize=10",
"count": 126
}
{
"errorCode": "INVALID_PRODUCT_NAME_FORMAT",
"errorMessage": "Invalid product name format, Special characters are not allowed (&,!,$,',@,#,!,<,?). Valid example's e.g 'cisco' ,'cisco_xe' ,'cisco-xe*' etc"
}
A total of 126 advisories are found for Cisco Identity Services Engine Software. If paginated with pageSize equal to 10, you get a total of 13 pages with only 6 advisories on the last page (page 13). However, page 13 shows:
{
"errorCode": "INVALID_PAGEINDEX",
"errorMessage": "Incorrect page index value"
}
Thank you,
02-23-2023 03:09 AM
@PR Oxman When an update is expected?
02-26-2023 04:20 PM
Hello Osama,
Just back from leave; will take a look later today and respond this week.
Thanks.
02-27-2023 11:41 AM
Hello Osama,
Issue #1 has been fixed in prod:
"paging": {
"next": "/product?product=Cisco Identity Services Engine Software&pageIndex=3&pageSize=10",
"prev": "/product?product=Cisco Identity Services Engine Software&pageIndex=1&pageSize=10",
"count": 127
}
Issue #2 is currently being worked and will provide an update when the fix will be delivered to prod.
Thanks
04-04-2023 02:53 PM
Hi Oxman,
Any updates on issue #2?
Thank you,
Osama
04-04-2023 08:34 PM
Hello Osama,
A fix will be deployed this Friday.
Regards
04-08-2023 05:52 PM - edited 04-08-2023 05:52 PM
Hi Oxman,
I can confirm that now the API is working properly.
Thanks a lot for the efforts.