API v4 for Qualys SSLLabs #189
Assignees
Comments
|
Hi @yoyoden, thanks for raising the issue. |
|
Great, thank you |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
Bumping to defeat the github-actions bot :) |
|
It seems that v3 and v4 do not have much change except v4 now requires to first register with an organisation email address, and then each api call needs to have that registration email in the request header. |
7 tasks
kyhau
added a commit
that referenced
this issue
Apr 7, 2024
- Support Qualys SSLLabs API v4 - The tool uses [API v4](https://github.com/ssllabs/ssllabs-scan/blob/master/ssllabs-api-docs-v4.md) if you provide your registered email with Qualys SSLLabs via the `--email` argument. - The tool uses [API v3](https://github.com/ssllabs/ssllabs-scan/blob/master/ssllabs-api-docs-v3.md) if you do not specify the `--email` argument. Note that v3 will be being deprecated in 2024 by Qualys. - Ticket: #189
|
Issue resolved. See https://github.com/kyhau/ssllabs-scan/releases/tag/3.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, just curious if you have plans or an ETA for supporting API v4 now that v3 has been deprecated? Thank you
https://notifications.qualys.com/api/2023/09/28/introduction-of-api-v4-for-qualys-ssllabs-and-deprecation-of-api-v3
The text was updated successfully, but these errors were encountered: