Skip to Content
Author's profile photo Michael Kummer

How to prevent Secure Login Client from automatically launching when macOS boots

Secure Login Client (SLC), part of SAP Single Sign-On, automatically launches when the macOS boots. That is often the desired behavior, but in my case, it wasn’t. So I wanted to share with you a simple way of preventing SLC from launching at boot time.

I have two user accounts on my iMac, a personal and a work account. I don’t need SLC for my personal account and thus didn’t want macOS from launching it for all logged in users.

To prevent SLC from launching at boot, open the Terminal.app and navigate to /Library/LaunchAgents.

cd /Library/LaunchAgents

There you will find a preferences file called com.sap.secureloginclient.plist. It’s a system-protected file so you will need sudo to edit it using your favorite editor. I used nano to open the file using the following command:

sudo nano ./com.sap.secureloginclient.plist

Sudo will prompt you to enter your account password.

Once you have opened the file in the editor, locate the following line (line 11):

<string>launchctl setenv SNC_LIB /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SNC_LIB_64 /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SSF_LIBRARY_PATH /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SSF_LIBRARY_PATH_64 /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;open /Applications/SecureLoginClient.app</string>

Depending on your screen size and resolution, you will probably have to horizontally scroll to the right for a bit until you see the “open /Applications/SecureLoginClient.app” command. Delete that command (the part in bold) and leave the rest as-is. The remaining line should look like this:

<string>launchctl setenv SNC_LIB /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SNC_LIB_64 /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SSF_LIBRARY_PATH /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;launchctl setenv SSF_LIBRARY_PATH_64 /Applications/SecureLoginClient.app/Contents/MacOS/lib/libsapcrypto.dylib;</string>

Then press CTRL + X and Y to save and exit nano.

Next time to restart your Mac, SLC will not start automatically. You may have to repeat the above steps after upgrading SLC to a new version because the installer is likely to overwrite the changes you have made.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Frank Kueppers
      Frank Kueppers

      A brief comment:

      Since Version 3.0 SP02 Patch 1, the Secure Login Client (SLC) for macOS is no longer started automatically on login. Instead SLC start is triggered when opening an SNC connection (e.g.SAP GUI) or using PKCS#11 (e.g. SSH).

      Alternatively, the autostart can be toggled via SLC Dock icon (Option - Open at Login).

      See SAP Note 2500984.