You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
We are using the Metrics Toolkit to get a list of APIs without a security policy. Currently it says one of our API's doesn't have a security policy, even though it has Client Enforcement version 1.3.2 (with capital E) All the other ones have Client enforcement version 1.2.x (no capital e on enforcement)
It appears as if this difference in version is causing the API to show up as insecure, could that be? Are there more people who have the same issue?
I hope I'm raising this issue in the right place, and please let me know if you require any info from me. This is the only difference I could think of that might cause the incorrect list, since all API's do have a security policy present.
Thanks in advance for your input.
Kind regards, Gerben
The text was updated successfully, but these errors were encountered:
Hello,
We are using the Metrics Toolkit to get a list of APIs without a security policy. Currently it says one of our API's doesn't have a security policy, even though it has Client Enforcement version 1.3.2 (with capital E) All the other ones have Client enforcement version 1.2.x (no capital e on enforcement)
It appears as if this difference in version is causing the API to show up as insecure, could that be? Are there more people who have the same issue?
I hope I'm raising this issue in the right place, and please let me know if you require any info from me. This is the only difference I could think of that might cause the incorrect list, since all API's do have a security policy present.
Thanks in advance for your input.
Kind regards, Gerben
The text was updated successfully, but these errors were encountered: