Missing support for CCID USB devices #3
jonasstrehle
started this conversation in
General
Replies: 2 comments 2 replies
-
Check out https://github.com/WICG/web-smart-card/blob/main/README.md! |
Beta Was this translation helpful? Give feedback.
1 reply
-
I don't think we need to pursue this topic further, until the Web Smart Card API is available. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I ordered the cyberJack® RFID basis for testing out the USB reading capability of the browser using WebUSB. This reader acts as a Chip Card Interface Device (CCDI)
However it seems like the Chromium team blocked quite a bunch of devices that used to be accessible via this API.
Summary
The following set of USB interface classes, which should not be claimed using the WebUSB API, will be explicitly blocked by Blink: Audio, Video, HID, Mass Storage, Smart Card, Wireless Controller (Bluetooth and Wireless USB). These interface classes are already mostly blocked by an operating system’s built-in class drivers. This change establishes consistency across platforms.
Motivation
The WebUSB API is designed to provide a mechanism for device manufacturers and developers to build applications supporting novel hardware on the web instead of through native apps. As explained in the original Intent to Ship for WebUSB, most USB devices fall into one of a number of standardized device classes for which there are already high-level APIs provided by the Web Platform. For each of these interface classes the high-level API is the supported path and WebUSB is the unsupported path.
So, maybe we need to think about an alternative approach... using a smart card NFC reader thats is not using CCDI. Is something like this even possible?
Just wanted to share some information with you!
Feel free to answer in this thread.
Beta Was this translation helpful? Give feedback.
All reactions