Domain change from injixo.com to peopleware.com
As we move our services to a new domain, you may need to take action on your side to ensure injixo continues to work smoothly. Please complete the following actions by December 31, 2024, and involve IT support as necessary.
If you have any trouble completing these actions, please raise them with your injixo customer success manager. Not completing these actions might result in service interruption.
For all steps below, add peopleware.com alongside injixo.com. Do not replace.
1. Establish Firewall exceptions
To access the new web pages, please allow web traffic to and from the new domain *.peopleware.com via port 443.
If you are using ActiveX-based features or custom SDK applications, you need to allow outgoing traffic to *.peopleware.com via port 45054, too (port 80 for injixo hosts prior to 2019).
For more detailed instructions, see Microsoft documentation.
2. Share URLs for WebSockets
We use WebSockets to send real-time updates to users in Shift Center, Schedules, and Real-Time Adherence.
The TCP-based secure WebSocket protocol allows faster transmissions than HTTP through port 443. The browser upgrades a standard HTTP connection to a WebSocket connection. If successful, the browser’s dev tools will show the corresponding HTTP 101 (Switching Protocols) status code when you load the page.
Shift Center requires WebSockets to work at maximum speed. If WebSockets are not available, AJAX polling is used instead. The other pages do not provide a fallback mechanism and show error messages or reconnection attempts if the WebSocket connection cannot be established.
To allow WebSockets connections, please add the following URLs to the allowlist of your firewall:
- https://shiftcenter.peopleware.com
- wss://shiftcenter.peopleware.com
- https://app.peopleware.com
- wss://ws.peopleware.com
3. Review proxy server setups
WebSockets rely on a persistent TCP connection. Unlike traditional HTTP requests, a WebSocket connection remains open once established. Make sure that your proxy server does not terminate such TCP connections. Popular proxy servers like Nginx or Apache have specific modules or directives to support WebSocket connections.
4. Set up Internet Explorer mode in Microsoft Edge
- Navigate to Control Panel or Start Menu > search for Internet Options > Security (tab) > Trusted Sites > Sites (button) and add *.peopleware.com to your browser's trusted sites.
- Open edge://compat in your Edge browser. This will show all sites that will be opened in Internet Explorer mode and the location of your site list XML file. For more detailed instructions, see Microsoft documentation.
- Replace the content of your site list XML with the example file below. Ensure that you replace "iwfm-xxxx" with the identifier of your iwfm system.
In this example, your identifier would be "iwfm-ky94r9q3". - In case you have firewalls in place, ensure that you allow outgoing traffic to *.peopleware.com via port 45054, too (port 80 for injixo hosts prior to 2019).
- Activate the new settings by clicking "Force update" in edge://compat.
- Validate your actions by following the "Validation" section below.
Example XML file:
<site-list version="1.0">
<!-- iwfm-xxxx must be your injixo host. You can find it in the URL of injixo WFM -->
<site url="https://ihs.peopleware.com/iwfm/">
<compat-mode>Default</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="https://iwfm-xxxx.injixo.com/iwfm/">
<compat-mode>Default</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="https://iwfm-xxxx.peopleware.com/iwfm/">
<compat-mode>Default</compat-mode>
<open-in>IE11</open-in>
</site>
<shared-cookie
domain=".injixo.com"
name="injixo_session"
source-engine="MSEdge">
</shared-cookie>
<shared-cookie
domain=".injixo.com"
name="iwfm_language_id"
source-engine="MSEdge">
</shared-cookie>
<shared-cookie
domain=".peopleware.com"
name="injixo_session"
source-engine="MSEdge">
</shared-cookie>
<shared-cookie
domain=".peopleware.com"
name="peopleware_session"
source-engine="MSEdge">
</shared-cookie>
<shared-cookie
domain=".peopleware.com"
name="iwfm_language_id"
source-engine="MSEdge">
</shared-cookie>
</site-list>
Validation
You can confirm that the actions have been executed correctly by using the new test site:
- In Edge, open https://ihs.peopleware.com/ie-test/ in a new private window, displaying a green checkmark if executed correctly:
Next, click "Start test" which redirects to https://ihs.peopleware.com/iwfm/ie-test/. It should detect your browser and the presence of the required cookies by showing green checkmarks. The IE symbol should be visible in the address bar, indicating that the page runs in Internet Explorer mode (as seen in the picture below).
In case Browser info shows failure: add<site url="https://ihs.peopleware.com/iwfm/"> <compat-mode>Default</compat-mode> <open-in>IE11</open-in> </site>
to the XML, click "Force update" in edge://compat, reload page, and repeat the test
In case any of Cookie info shows failure: add<shared-cookie domain=".peopleware.com" name="xxxx" source-engine="MSEdge"> </shared-cookie>
to the XML, click "Force update" in edge://compat, reload page, and repeat the test. ("xxxx" is the name of the missing cookie, e.g. "injixo_session".) - Log into injixo and visit iwfm (https://www.injixo.com/iwfm/). The displayed URL should read something like this: https://iwfm-xxxx.injixo.com/iwfm (with "iwfm-xxxx" being your unique identifier). The Internet Explorer symbol should be visible in the address bar. If not, please compare your site list to the XML example file and ensure it contains a site URL block that looks like this (with "iwfm-xxxx" being your unique identifier):
<site url="https://iwfm-xxxx.injixo.com/iwfm/"> <compat-mode>Default</compat-mode> <open-in>IE11</open-in> </site>
- In the current URL, replace the "injixo" part with "peopleware". The displayed URL should read something like this: https://iwfm-xxxx.peopleware.com/iwfm (with "iwfm-xxxx" being your unique identifier). Be aware that the page might be blocked or unreachable for now. Nevertheless, the IE symbol should be visible in the address bar to indicate that the page is opened in IE mode. If not, please compare your site list to the XML example file and ensure it contains a site URL block that looks like this (with "iwfm-xxxx" being your unique identifier):
<site url="https://iwfm-xxxx.peopleware.com/iwfm/"> <compat-mode>Default</compat-mode> <open-in>IE11</open-in> </site>
Hint: In case you encounter login problems shortly after the test you probably haven't used a private tab ("incognito mode"). In this case, you need to clear the cookies for injixo.com and peopleware.com in the browser settings.