Developer feedback

[zgroza]

Please use the comments under this issue to submit your general feedback on this API.

If possible, please mention the name of the company you work for and the use case you have in mind for this API—this helps browser vendors set prioritization for implementing it. The processes of some browser vendors take such "web developer signals" into consideration when deciding whether the API should be shipped.

[ksranjan]

Hi, I am working at Omnissa on the Horizon Web, Chrome, and IWA clients.

We are looking forward to this smartCard API, which delivers significant advantages for our Horizon IWA client:

Secure Authentication: The API enables secure logon and identity verification by supporting enterprise-grade smart cards and PINs for Horizon Broker Authentication.
Seamless Smart Card Redirection: In VDI scenarios, the API facilitates smart card redirection at the PC/SC level, allowing remote virtual desktops and applications to access users’ smart cards as if they were directly connected. This ensures compatibility with existing enterprise workflows and applications.
Digital Signing & Encryption: Applications within remote sessions can leverage smart cards for digital signing and encrypting documents and emails.
Adopting this API will help us achieve feature parity with other Horizon native clients and significantly boost the user experience, as users will benefit from a familiar, seamless smart card experience across remote sessions.

[martinsarvas]

Hi, I am working at ACRE (previously TDS) on the chrome OS visitor kiosks.
We are in the middle of the migration from chrome app to IWA which needs a Smart Card Connector app and we would like to use this new Web Smart Card API.

Secure Authentication: The host is capable to securely authenticate with the company card using the Smart Card API to gain access to restricted section on the visitor kiosk and allow additional functionality. e.g. printing a visitor label

Remote Configuration: Visitor kiosk can be in remote locations without staffed lobby, which means a remote reconfiguration is a must have - with this API we are able to do it for a specific badge reader

Extended manipulation: The API also provides an easier usage of more complex card operations, which are not available in keyboard wedge mode of the reader. e.g. support for PIV