Booting with the token already inserted does not work. It is a USB token, so maybe some part of the USB system is not yet up at that point of the boot.
I'm not sure about the workaround. I can see it leading to confusion: "why do some configurations autostart and not others?". However, it would definitely avoid the problem at hand, of course. Ideally, such configurations should be autostarted when a user is logged in, and can use a management interface.
Let me know if you go with a workaround based on "pkcs11-id", and I will test it.
Hi Thierry,
Booting with the token already inserted does not work. It is a USB token, so maybe some part of the USB system is not yet up at that point of the boot.
I'm not sure about the workaround. I can see it leading to confusion: "why do some configurations autostart and not others?". However, it would definitely avoid the problem at hand, of course. Ideally, such configurations should be autostarted when a user is logged in, and can use a management interface.
Let me know if you go with a workaround based on "pkcs11-id", and I will test it.