Hi all, which minimum Version of IGEL OS is working and supported for Imprivata SSO?
E.g. Customer has different OS v4 Versions in use. Is there an Overview with the Firmware Builds?
Thanks and Regards,
Hi, that’s the last I have: docplayer.net/96981504-Imprivata-onesign-supported-components-last-updated-september-21-2018.html
Hi Sebastien,
thanks. but this article seems to be to new. I found this one and there is v4 mentioned:
kb.igel.com/files/4257754/8618432/1/1544791014355/en_udlx.pdf
And in this one:
www.lanline.de/it-security/sichere-authentifizierung-fuer-thin-clients.12309.html
…
Mit den Firmware-Updates 4.13.100 und 5.02.100 integriert Igel die Authentifizierungslösung Imprivata Onesign Proveid Embedded auf all seinen x86-basierten Thin und Zero Clients.
…
Igel betont, man habe den Imprivata-Support auch für die Igel-Linux-Version 4 integriert, sodass Bestandskunden ebenfalls davon profitieren könnten.
…
Can you confirm this and also the Version 4.13.100?
I can guarantee that Imprivata OneSign ProveID Embedded is included in latest v4 but cannot guarantee the function, since v4 is out of support 😄
Continue reading and comment on the thread ‘Which minimum Version of IGEL OS is working and supported for Imprivata SSO?’. Not a member? Join Here!
Learn more, search the IGEL Knowledge Base
Ask a question or comment on the above message thread?
Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.Submit a question, or Join Today!
Popular Message Threads
- How to Install IGEL OS via a Bootable USB Drive
- Error “AM_ERROR_AUTH_NETWORK_ERROR [65275]” adding store in Citrix Workspace App version 20.x on IGEL OS 11.04
- Receiving error: “Citrix Receiver cannot create a secure connection in this browser” when launching a secure connection from Firefox on IGEL OS
- Error connecting to Citrix StoreFront “Error adding store: Http error[302]”
- How to change the default IGEL UMS admin password?
- IGEL UD3 (LX50) randomly get this error with Citrix: The X Request 130.1 caused error :”10: BadAccess ( attempt to access private resource denied) any ideas?
- Where to delete the certificates that cause ‘invalid certificate’ when trying to import an IGEL into UMS?