在Microsoft Edge环境下基于JavaScript/Angular生成本地计算机唯一可预测ID的技术方案咨询

Great question—given your constraints (Microsoft Edge-only, no local services allowed, backend needs to map to pre-defined device-specific pages), here are the most practical, Edge-compatible approaches:

1. Windows Integrated Authentication (NTLM/Kerberos) – Best for Enterprise Domain Environments #

If your devices are joined to a corporate Active Directory domain, this is the most reliable and low-effort option:

• How it works: Edge automatically sends domain authentication credentials when accessing intranet sites configured for integrated auth. Your backend can extract either the device's security identifier (SID) or computer name from the authentication context.
• Implementation steps:
  • Configure your web server (e.g., IIS, Apache) to enable Windows Integrated Authentication for your target domain (www.foo.com).
  • On the backend, retrieve the device identifier from the request. For example, in IIS you can use Request.ServerVariables["HTTP_X_FORWARDED_USER"] or direct SID lookup via server APIs.
  • Map the retrieved identifier to the pre-defined device-specific page (e.g., www.foo.com/A for device A) and trigger a redirect.
• Pros: No front-end code required, fully supported by Edge, secure and tamper-resistant, backend can pre-map all domain devices in advance.
• Cons: Only works if devices are part of an AD domain; won't work for non-domain environments.

2. Pre-Write Device IDs to Edge's Local Storage via Enterprise Management Tools #

If you have access to enterprise device management platforms like Microsoft Intune or Group Policy, you can pre-configure a unique device ID directly in Edge's storage:

• How it works: Use Intune/Group Policy to deploy a script that runs when Edge starts, writing a unique, pre-defined device ID to localStorage or sessionStorage for your target domain.
• Implementation steps:
  • Create a small JavaScript script (e.g., localStorage.setItem("corpDeviceId", "DEVICE_A")) tailored to each device.
  • Deploy the script via Intune's "Custom Policy" or Group Policy's "Script Extension" for Edge.
  • On your www.foo.com landing page, add a simple script to read the ID:

    const deviceId = localStorage.getItem("corpDeviceId");
    if (deviceId) {
      window.location.href = `/${deviceId}`;
    }
    

• Pros: Simple to implement, Edge fully supports localStorage, backend can pre-know all device IDs in advance.
• Cons: Requires access to enterprise device management tools; relies on the script being successfully deployed to each device.

3. Client Certificate Authentication #

If your organization can manage digital certificates, this provides a highly secure, unique device identifier:

• How it works: Issue a unique client-side SSL certificate to each Edge device, configured to automatically present the certificate when accessing www.foo.com. Your backend can extract the certificate's serial number or common name (CN) to identify the device.
• Implementation steps:
  • Use your corporate PKI to generate unique certificates for each device.
  • Configure Edge via Group Policy/Intune to trust the certificate authority and auto-select the certificate for your domain.
  • On the backend, extract certificate details from the incoming HTTPS request and map to the device-specific page.
• Pros: Extremely secure and tamper-proof, Edge supports client certificates natively.
• Cons: Requires PKI infrastructure and certificate management overhead; higher deployment complexity.

What to Avoid #

• WebRTC Private IP Lookup: As you noted, Edge has never supported this, and modern browsers have restricted it for privacy reasons.
• Generic Browser Fingerprinting: Tools that generate fingerprints from browser specs (user agent, screen resolution, etc.) are not backend-predictable—you can't pre-map these values to specific devices in advance, and they can change (e.g., after an Edge update).
• Local Services: You've already ruled this out, but it's worth confirming that deploying local agents/servers isn't necessary with the above options.

内容的提问来源于stack exchange，提问作者Wolfgang Jagomir