AI 产品解读Chrome-native messaging bridge enabling e-signature (digital signature) operations for QNB eSolutions Portal
Chrome version 45 dropped Java support, breaking Java-based e-signature functionality. This extension provides a native messaging workaround so users can perform e-signature, e-Ledger (e-Defter), and KEP (Registered Electronic Mail) transactions on QNB eSolutions Portal via Chrome.
User visits QNB eSolutions Portal → triggers e-signature operation → portal dispatches parameterEvent → content script (baglan.js) reads parameters from chromeParameters element → sends message to background (arka.js) → background connects to native messaging host 'com.google.chrome.native.applet' → native e-signature app processes signing → response flows back through background to content script → content script dispatches signatureEvent with the result to the portal page
Bridges Chrome browser to locally installed e-signature native application via chrome.runtime.connectNativeContent script listens for parameterEvent from QNB eSolutions Portal pages and forwards signing parameters to native appReturns native app responses (signatures) back to the web page via custom signatureEventDisplays Chrome notifications when the signing applet is launchedSignals extension presence to the portal via injected DOM elements (CSChromeExtension, CSChromeExtensionVersion)
- 目标用户
- QNB eSolutions Portal users who need e-signature capabilities in Chrome / Turkish businesses using e-Defter (e-Ledger) and KEP (Registered Electronic Mail) services
- Cannot inspect the native e-signature application (separate download from qnbesolutions.com/programlar/) to determine if it has paid features or requires license activation
- Cannot verify QNB eSolutions Portal's actual authentication/account requirements from extension source alone
- The extension runs on all HTTP/HTTPS pages (content_scripts matches */*/*) which is broad but necessary for its bridge functionality
付费分析未识别到付费功能
The extension source code contains no payment logic, no subscription checks, no premium feature gating, no billing API calls, and no upgrade UI. The keyword matches for 'pro' and 'license' in the static scan are false positives: 'pro' appears in base64-encoded verified_contents metadata, and 'license' refers to the Chromium BSD-style open-source license header in arka.js. The extension is purely a message-passing bridge with no feature differentiation. The destination service (QNB eSolutions) may have paid business plans, but the extension itself does not gate any functionality behind payment.
- 置信度
- 90
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 是
- 登录理由
- The extension itself does not implement login UI or authentication logic. It is a native messaging bridge that connects the Chrome browser to a local e-signature application. However, its entire purpose is to enable e-signature operations on the QNB eSolutions Portal (as stated in the store description: 'Google Chrome tarayıcısı ile QNB eSolutions Portal'e e-İmza ile girip, e-Defter ve KEP işlemlerini gerçekleştirebilmeniz mümkündür'). The QNB eSolutions Portal requires an account to access and perform these business transactions. The extension cannot fulfill its core workflow without the user being logged into the destination service.