AI product readBrowser bridge/connector for hardware security authenticators (smart cards, YubiKeys, passkeys) via native messaging to a PCSC (Personal Computer/Smart Card) service
Web applications cannot directly access hardware security devices like smart cards and security keys. This extension provides a bridge between web pages (using the Axiad WebPCSC SDK) and the operating system's PCSC layer via a native messaging host, enabling lifecycle management of passkeys, smart cards, and security keys from within the browser.
1. User installs the Axiad Conductor Browser Extension and a native WebPCSC host app. 2. A web application embeds the WebPCSC SDK, which creates a DOM element with id 'com.axiadids.pcsc'. 3. The content script (fg.js) detects this element and connects to the extension's background service worker. 4. The extension checks a whitelist to determine if the web host is allowed to access hardware devices. 5. If allowed, the extension forwards PCSC operations (list readers, connect to card, send APDUs) via native messaging to the native host. 6. Responses are relayed back to the web application through DOM custom events (PCSC-out).
Bridge between web apps and native PCSC smart card reader serviceHost whitelist management for controlling which web domains can access hardware authenticatorsSupport for list, connect, disconnect, info, and send APDU operations to smart cards/readersAdmin-managed configuration via chrome.storage.managed (whitelist lockdown)Diagnostics panel for troubleshooting native host and hardware connectivitySupport for Windows Hello for Business (WHFB) and Virtual Smart Card (VSC) operations
- Target users
- Enterprise IT administrators managing smart card / PKI infrastructure / End users authenticating with hardware security keys (YubiKeys, smart cards) in enterprise web applications / Developers integrating Axiad Conductor or WebPCSC SDK into web applications
- No store detail screenshots or user reviews analyzed for UX confirmation
- The native companion app (WebPCSC) source is not included — only the extension side is analyzed
- Edge-specific shim file (edge/bg.js) not fully analyzed but appears to be a polyfill for Edge compatibility
MonetizationNo paid features detected
No payment processing, subscription gating, license keys, or upgrade UI found in the extension source. The only 'upgrade' reference (opt/page.js line 74: 'Please upgrade WebPCSC for more details') refers to upgrading the native companion binary version, not a paid tier. No Stripe, no billing APIs, no plan-check logic. The 'pro' keyword hits are all JavaScript Promise usage, not 'pro plan' references.
- Confidence
- 90
- Payment platform
- --
- Source
- AI / High
- Login required
- No
- Reason
- The extension does not implement any user account login flow. It is a local bridge between web pages and a native messaging host (WebPCSC / com.axiadids.pcsc). The 'auth' operations found in code (backgrounds.js lines 620-624) refer to hardware authenticator APDU operations (smart card/YubiKey authentication commands), not user account authentication. The extension uses chrome.storage.sync for whitelist data and chrome.storage.managed for admin-pushed config, neither of which require the user to log in to an account. There is no OAuth, no session tokens, and no credential entry UI.