Login

Licensing the device

In the login screen, enter the Licence Key to license the device and press LICENSE DEVICE.
1. Alternatively, press DEMO MODE if the application is to run against EPICOR demo system with configured EPIC06 or EPIC03 company or EpicorE6 in cloud educational environment.
Press DEVICE to see how this device will be identified by the licensing system.

Terms

Toggle the I accept button.
Tap on CONTINUE.

Server URL

Enter the Server URL in a format https://[MyAppServerHost]/[MyAppServerInstance] and click CONTINUE. ("https://" may be omitted when typing server URL)

An error message will indicate if the Server URL provided is incorrect.

Enter your User Name and Password and click LOG IN.

️ This option is applicable to devices with an internal scanner and also devices that have no internal scanners but have cameras i.e. mobile phones

Tap on the “Scan a QR Code with connection information” icon to use camera to scan the QR Code.

Tap on the toggle bar to Allow modifying system settings on the device.
Repeat the step and tap on the Scan a QR Code with connection information icon and select Allow.

Tap on the Scan a QR Code with connection information icon and the camera will open up and allow to scan a QR code.

QR Code must contain the information of the Username and the ServerURL

a. Creating a Barcode

Generate a QR Code using a QR code generator site such as the following:
1. https://barcode.tec-it.com/en/QRCode?data=This is a QR Code by TEC-IT or https://www.qr-code-generator.com/
Enter a code following the following format:

{"username":"myusername","serverUrl":"myserverurl"}

Replace “myusername” with the user’s epicor account username: epicor
Replace “myserverurl” with the user’s server url: [MyAppServerHost]/[MyAppServerInstance]
The final code format should look like the following:

{"username":"epicor","serverUrl":"[MyAppServerHost]/[MyAppServerInstance]"}

Save and use the following generated barcode to login using QR scanner.

️ Since Chrome version 121.0.6167.101 there are new requirements for use of private self-signed SSL certificates

To be able to connect and log in to a server configured with self-signed SSL certificate, the certificate needs to include “Digital Signature” in “Key Usage” field.

Self-signed certificates created in Windows Server 2022 or Windows 11 include “Digital Signature” in “Key Usage” field by default. On older versions of Windows Server hosting the Epicor application the certificates will have to be replaced with a correct certificate.

How To achieve self-signed certificates

Exported self-signed from Windows Server 2022 or Windows 11.
Copy on to the server.
Import and use in https bindings configuration.
- Alternatively, a new certificate including “Digital Signature” in “Key Usage” field could be generated using tools such as PowerShell, OpenSSL or similar.

Azure AD Authentication

Before using Azure AD authentication in EMW versions 3.3.3 and higher, the following Redirect URI https://emwkineticapp/ needs to be added to Azure AD Registered Client Application to allow EKW to be authenticated with Azure AD.

Redirect the address for EKW and ensure it is entered against the AD Application (client) ID

That appears in EPICOR Azure Active Directory Configuration Maintenance and was set up in Azure for Epicor client access (i.e. http://localhost)

When connecting to EPICOR server configured for Azure AD Authentication Microsoft logon pages are presented instead of regular login screen shown above.