Skip to main content
syulv
Explorer
Jun 23, 2024 10:20 PM UTC
Question

Fortinetclient SSL VPN Unable to use system's key store / Object does not exist at path

Hello,

 

I'm trying to configure a simple SSL VPN using FortiClient on a fresh install of Ubuntu 22.04.4 LTS.

 

Fortigate seems to be correctly configured (7.2.8): used from MacOSX, and Windows works flawlessly.

 

I'm installing a Linux Fortinate client using CLI (no GUI) - FortiClient Version: 7.2.4.0809 (installed following section "Ubuntu 22.04 LTS" for 7.2 from https://www.fortinet.com/support/product-downloads/linux ).

 

Setting up a new connection seems trivial:

ubuntu@ip:~$ forticlient vpn edit myvpn
=====================
Edit personal VPN profile:myvpn
=====================
Type (1.SSL VPN / 2.IPsec VPN) [default=1]: 1
Remote Gateway: 1.2.3.4
Port [default=443]: 7443
Authentication (1.prompt / 2.save / 3.disable) [current=prompt]:1
Certificate Type (1.local (pkcs12) / 2.smartcard (pkcs11) / 3.disable) [current=disable]:3

Hovewer, after the last response during the above configuration stage, I was initially getting:

Unable to use system's key store: The name org.freedesktop.secrets was not provided by any .service files.
DONE.

After that, I found the information below should alleviate the issue (please remember that my environment is CLI only):

sudo apt install gnome-keyring

This changed the error to:

Unable to use system's key store: Object does not exist at path “/org/freedesktop/secrets/collection/login”.
DONE.

Also, ignoring the above errors (if this is not just an informational message) and trying:

ubuntu@ip:~$ forticlient vpn connect myvpn

I am getting the following error:

terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr: __pos (which is 26) > this->size() (which is 24)
Aborted (core dumped)

Any idea how to approach troubleshooting or what may resolve this issue? What am I missing?

 

Thanks.

 

Regards,

S.

5 replies

AlexC-FTNT
Staff
Staff
Jun 24, 2024 8:01 AM UTC

Once you iinstall the gnome keyring, you must also initialize it. 

Have you done this?

 

Initialize and unlock the login keyring:

$ killall gnome-keyring-daemon
$ echo -n “your-login-password" | gnome-keyring-daemon --unlock

https://docs.fortinet.com/document/forticlient/7.0.0/administration-guide/41299/appendix-e-forticlient-linux-cli-commands#To_configure_gnome_keyring_

(bottom of page)

syulv
syulvAuthor
Explorer
Jun 24, 2024 11:31 AM UTC

Thank you. @AlexC-FTNT . This did help!

Instead of double quotes, single quotes are required, it seems, as otherwise, the command does not pipe over correctly and gets stuck, so:

echo -n 'your-login-password' | gnome-keyring-daemon --unlock

Still, when I try:

ubuntu@ip:~$ forticlient vpn connect myprofile

I get:

terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr: __pos (which is 26) > this->size() (which is 24)

(before attempting to connect, I had created a new profile from scratch, which came up without any previous keyring-related errors)

 

Perhaps I'm still doing something wrong regarding keyring-daemon (I'm unsure how to force it to log more verbose)? Is there any chance this is a bug of some sort?

 

Also, if I explicitly ask for credentials every time, why do I need to bother with gnome-keyring-daemon at all? Is it possible to disable this functionality entirely (it also increases the space footprint to install extra packages)?

AlexC-FTNT
Staff
Staff
Jun 24, 2024 11:50 AM UTC

I'm not sure I know what to suggest further. Let's see if others have more ideas.

This was a step that is often missed, so I wanted to make sure it was performed

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024