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
{{ message }}
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.
Safenet now offers USB-C tokens which are currently not fully recognized by Fortify. I can see the token in the software but it shows as "read only" mode. The device shows as "SCard Windows API."
I have seen this before and it usually means that Fortify does not recognize the ATR for this device. Could you please look into this and add the ATR to the SCard.json like you have done in the past?
In the fortify logs I see the following information:
CryptoAPI","level":"info","message":"certStorage/exportCert","source":"server-api","timestamp":"2024-01-04T16:34:04.608Z"}
{"atr":"3bff9600008131fe4380318065b0846160fb120ffd8290000c","level":"info","message":"cardReader/insert","reader":"SafeNet eToken 5300 C 0","source":"server-api","timestamp":"2024-01-04T16:34:04.613Z"}
The text was updated successfully, but these errors were encountered:
Safenet now offers USB-C tokens which are currently not fully recognized by Fortify. I can see the token in the software but it shows as "read only" mode. The device shows as "SCard Windows API."
I have seen this before and it usually means that Fortify does not recognize the ATR for this device. Could you please look into this and add the ATR to the SCard.json like you have done in the past?
In the fortify logs I see the following information:
CryptoAPI","level":"info","message":"certStorage/exportCert","source":"server-api","timestamp":"2024-01-04T16:34:04.608Z"}
{"atr":"3bff9600008131fe4380318065b0846160fb120ffd8290000c","level":"info","message":"cardReader/insert","reader":"SafeNet eToken 5300 C 0","source":"server-api","timestamp":"2024-01-04T16:34:04.613Z"}
The text was updated successfully, but these errors were encountered: