Fortify Not Detected on MacOS M2 Sonoma

[PeterGS123]

I have a customer who installed Fortify on a M2 MacBook running MacOS Sonoma. The software installs successfully. It appears to be running because the icon is showing at the top of the screen with other software that is running in the background. When clicking on the fortify app icon, the customer is able to select the "tools" option.

The page opens in Google Chrome and we receive an error messaging saying that fortify is not running. There is a button "try again" or "I don't have one." indicating that fortify needs to be installed. The same error message is displayed when going to tools.fortifyapp.com using the safari browser.

We have tried to exit the software and restart it. We have also restarted the computer. We have the version of the software installed that was built for apple silicon. Are there other steps that we need to try? I tried to attach logs exported from the chrome browser in HAR format however Hithub does not support this file type.

I reviewed the logs and found an error about the certificate validity which I don't know if this is related to an SSL certificate or code signing certificate:

"redirectURL": "",
"headersSize": -1,
"bodySize": -1,
"_transferSize": 0,
"_error": "net::ERR_CERT_AUTHORITY_INVALID",
"_fetchedViaServiceWorker": false
},
"serverIPAddress": "",
"startedDateTime": "2025-01-02T19:20:13.989Z",
"time": 6.188000000292959,
"timings": {
"blocked": 6.188000000292959,
"dns": -1,
"ssl": -1,
"connect": -1,
"send": 0,
"wait": 0,

      "receive": 0,
      "_blocked_queueing": -1
    }
  },

  {
    "_initiator": {
      "type": "script",
      "stack": {
        "callFrames": [
          {
            "functionName": "isConnectionDetected",
            "scriptId": "11",
            "url": "https://tools.fortifyapp.com/assets/index-CAqIlJty.js",
            "lineNumber": 266,
            "columnNumber": 1433
          },

fortify logs.txt

[Kharya1337]

Hello,

Thank you for reaching out. To help us analyze the issue, could you please enable logging in Fortify and share the log file with us?

Steps to Enable Logging:

1. Open the file located at ~/.fortify/config.json.
2. Update the file by setting "logging": true.
3. Save the file.
4. Relaunch Fortify.

The log file will be created at ~/.fortify/fortify.log. Please share this file with us so we can investigate further.

Also based on the error message "_error": "net::ERR_CERT_AUTHORITY_INVALID", we recommend trying the following additional step:

Fix for SSL Certificate Issue:

1. Remove the file located at ~/.fortify/cert.key.
2. Relaunch the application.

This will prompt Fortify to reissue the SSL certificate, which should resolve the issue.

Let us know how it goes or if you need further assistance.

Best regards,
Illia

[PeterGS123]

Hello Illia,

In your response you asked me to delete the file located in this folder: ~/.fortify/cert.key. Does this apply to MacOS users? I am not sure where to find that folder but I will try.

My customer has sent me logs from fortify. We enabled fortify, exited the program, and then reloaded it. Then we tried to open up fortify tools and we received the same error message. I have attached a screenshot of the error.

After following those steps, the customer sent me the logs from Fortify which I have pasted below:

{"level":"info","message":"Check for new update","source":"update"}
{"level":"info","message":"New version wasn't found","source":"update"}
{"lev-el":"info","message":"Starting","source":"application","time":1736278073669,"version":"2.0.3"}
{"level":"info","message":"System in-fo","source":"system","platform":"Darwin","arch":"aarch64","cpus":8,"version":"14.4.1","totalmem":17179869184,"freemem":60653568}
{"level":"info","message":"Screen size","source":"system","width":1440,"height":900}
{"level":"info","message":"Firefox profiles directory does not exist","source":"firefox-providers","dir":"/Users/josesubero/Library/Application Support/Firefox/Profiles"}
{"level":"info","message":"No Firefox profiles found","source":"firefox-providers"}
{"level":"info","message":"Check for new update","source":"update"}
{"level":"info","message":"Get certificate status","source":"ssl-service","status":"valid"}
{"level":"info","message":"Profiles folder does not ex-ist","source":"firefox","path":"/Users/josesubero/Library/Application Sup-port/Firefox/Profiles"}
{"level":"info","message":"SSL certificate is loaded","source":"server"}
{"level":"info","message":"Comparing current version of card.json file with re-mote","source":"server"}
{"level":"info","message":"New version wasn't found","source":"update"}
{"level":"info","message":"card.json has the latest ver-sion","source":"server","version":"1.1.20"}
{"level":"info","message":"Started","source":"server","address":"127.0.0.1:31337"}
{"level":"info","message":"PKCS#11 library infor-mation","source":"provider","library":"/Applications/Fortify.app/Contents/MacOS/libpvpkcs11.dylib","manufacturerId":"Module","cryptokiVersion":{"major":2,"minor":30},"libraryVersion":{"major":1,"minor":4},"firmwareVersion":{"major":0,"minor":1}}
{"level":"info","message":"Crypto provider was added to the list","source":"provider","library":"/Applications/Fortify.app/Contents/MacOS/libpvpkcs11.dylib","name":"MacOS Crypto","reader":"MacOS Crypto"}
{"level":"info","message":"Start PCSC listening","source":"pcsc"}
{"level":"info","message":"PCSC connected successfully","source":"pcsc"}
{"level":"info","message":"Initialize new reader","source":"pcsc","reader":"SafeNet eToken 5100"}
{"level":"info","message":"New token was added to the read-er","source":"pcsc","reader":"SafeNet eToken 5100","atr":"3bd5180081313a7d8073c8211030"}
{"level":"info","message":"Token was added to the read-er","source":"provider","reader":"SafeNet eToken 5100","name":"SafeNet eToken 5110","atr":"3bd5180081313a7d8073c8211030"}
{"level":"info","message":"Loading PKCS#11 li-brary","source":"provider","library":"/usr/local/lib/libeTPkcs11.dylib"}
{"level":"info","message":"Looking for slot","source":"provider","slots":1}
{"level":"info","message":"Use ConfigTemplateBuild-er","source":"provider","template":{"generate":{"private":{"token":true,"extractable":false,"sensitive":true}}}}
{"level":"info","message":"PKCS#11 library infor-mation","source":"provider","library":"/usr/local/lib/libeTPkcs11.dylib","manufacturerId":"SafeNet, Inc.","cryptokiVersion":{"major":2,"minor":20},"libraryVersion":{"major":10,"minor":8},"firmwareVersion":{"major":0,"minor":0}}
{"level":"info","message":"Crypto provider was added to the list","source":"provider","library":"/usr/local/lib/libeTPkcs11.dylib","name":"SafeNet eToken 5110","reader":"SafeNet eToken 5100"}
{"level":"info","message":"Amount of tokens was changed","source":"provider-service","added":1,"removed":0}

[microshine]

Fortify uses SSL connection with clients. To make browsers trust the certificate, you need to install the root certificate. On MacOS, this can be done in two ways: through Keychain Access or through the Fortify application.

Method 1: Manual Installation via Keychain Access

1. Download and install the certificate located at ~/.fortify/ca.pem (~/ is your user's home directory)
2. To open Finder in the home directory, use the command open ~/.fortify
3. Import the certificate into Keychain Access
4. Change its trust settings to Always Trust

Method 2: Automatic Installation via Fortify

Fortify can install the certificate automatically when generating a new one:

1. Delete the following file from ~/.fortify:

• cert.pem

2. The next time you launch Fortify, it will prompt you to create and install a new certificate
3. A dialog box will appear

During installation, the OS will request your user password to access Keychain Access. You must enter the password to install the certificate; otherwise, the installation will fail.

Verification

After installing the certificate, browsers will trust the SSL connection with Fortify.

To verify the certificate installation, visit https://127.0.0.1:31337/.well-known/webcrypto-socket in your browser. If the certificate is installed correctly, the browser will display JSON connection information.