I work for a Health Care organization and over this past weekend my Help Desk received at least 2 calls from Doctors (who use Mac Computers) stating that after a Mac OS update, their Soft Token was detected as a virus and was deleted from their system. I’m not sure how many Mac computers we have in the field but so far we only had those 2 users with that issue. Our work around was to have the Doctors put the Soft Tokens on there phones. My question, is any else having this Mac OS related issue?
I've moved your question to the RSA SecurID Access space where it will be seen by the product's support engineers, other customers and partners. Please bookmark this page and use it when you have product-specific questions.
Alternatively, from the RSA Customer Support page, click on Ask A Question on the blue navigation bar and choose Ask A Product Related Question. From there, scroll to RSA SecurID Access and click Ask A Question. That way your question will appear in the correct space.
Regards,
Erica
Can you please let me know what version of the RSA SecurID token application is installed on your macOS machines? Also, what update was pushed out to them?
Regards,
Erica
We have not seen this issue with RSA SecurID Software Token 4.2.1 for Mac OS X on Catalina/macOS 10.15.3. We are not aware of any other users that reported the same issue.
We will investigate further and get back to you.
Regards,
Erica
I am working a case with a customer where they had a MAC with Software Token SWT v. 4.1.2 which was working until they updated MAC OS to 10.14.6, which broke the existing token database. They had to uninstall the Software Token App, and installed a later version of SWT v. 4.2.1, but cannot import this token via CTKip. I think it has something to do with different supported Ciphers in the newer MAC OS, so that decryption of the token database and encryption /decryption of the CTKip URL link to securely import the token does not work.
It's possible a reinstalled SWT app could import a token via .sdtid file.
Unfortunately you may need to open a support case to get to the bottom of this.
Thanks for providing the details, Jay. We suspected that the issue had to do with running the old SoftToken build v4.1.2 on Catalina.
As far as SWT v4.2.1 kit, it requires TLS1.2 for ct-kip.
If customer AM instance is not configured to require/accept TLS1.2, then ct-kip will fail.
We have not qualified SWT v4.1.2 on Catalina yet – we are in fact in the middle of doing so.
We will let you know as soon as we can if .STDID file import will work and/or if we need to generate a new kit for Catalina. Would you please open a support case for this. Thanks!
Thanks for providing the details, Jay. We suspected that the issue had to do with running the old SoftToken build v4.1.2 on Catalina.
As far as SWT v4.2.1 kit, it requires TLS1.2 for ct-kip.
If customer AM instance is not configured to require/accept TLS1.2, then ct-kip will fail.
We have not qualified SWT v4.1.2 on Catalina yet – we are in fact in the middle of doing so.
We will let you know as soon as we can if .STDID file import will work and/or if we need to generate a new kit for Catalina. Would you please open a support case for this. Thanks!