Getting started
Authentication and authorization
Your organization needs to have a Single Sign-on solution for IQNECT to use. See SSO Introduction.
- Both SAML 2.0 and OIDC are supported
- We have validated IQNECT to work with OKTA, MS, Google, and AWS Cognito. You can find additional information about the setup on this page.
Depending on your needs, either all users from the identity provider can be allowed to access IQNECT or just a limited set of named users. For the named users, prepare a CSV file containing the SSO IDs or emails.
PTC Codebeamer
One or more PTC Codebeamer environments within your organization can be connected to IQNECT
- Versions 2.1, 2.2, and 3.0 are supported
- Some updates need to be performed to Codebeamer application configuration
Networking Requirements
This next section contains details about the traffic IQNECT generates at a specific customer installation, and describes the domain names that must be allowed through the firewall to ensure that IQNECT functions as expected.
Users Browser
The IQNECT Frontend (currently embedded inside Codebeamer) generates outgoing traffic to the following domains over HTTPS. Note that the origin of this traffic is the user's browser, so the policy needs to be applied to all devices of users who are using IQNECT.
- Outgoing traffic
app.iqnect.ai: loads web assets (js, html, css, images), uploads large payloads (with images, etc)api.iqnect.ai: loads data (semantic search results, analysis, etc)support.iqnect.ai: for our support page.beaconapi.helpscout.net,beacon-v2.helpscout.net: for our embedded support tool (if enabled at the customer)
Codebeamer Server
In order for the IQNECT Codebeamer Extension to function, the following firewall traffic needs to be allowed. Note that all these rules apply only to the server running Codebeamer.
- Outgoing traffic, using HTTPS
api.iqnect.ai: send data whenever an item changesapp.iqnect.ai: to upload bigger payloads for analysis (e.g,. items with lots of images)