Authentication overview

ITIS (IT'IS Foundation) specializes in advanced computational modeling and simulation software for electromagnetic and acoustic fields, primarily in biomedical applications. Their core products, such as Sim4Life and SEMCAD X, are sophisticated desktop applications designed for scientific research, industrial development, and regulatory compliance. Consequently, authentication for ITIS products focuses on ensuring authorized access to these specialized software platforms rather than typical API-based authentication models common in web services.

Authentication for ITIS software is primarily managed through a licensing system that validates user entitlements to run the software. This involves obtaining and installing specific license files, often tied to a hardware identifier or a network license server. User accounts within the software itself provide further access control and personalization, managing settings and project data. This approach aligns with the use case of high-performance scientific computing, where software is installed locally or on dedicated compute clusters, and access is controlled at the application level rather a public API endpoint.

The ITIS documentation portal provides comprehensive guides on installing, licensing, and managing their software products, detailing the specific steps required for various deployment scenarios, including single-user installations and network license configurations. For example, the ITIS documentation outlines the process for setting up Sim4Life licenses.

Supported authentication methods

ITIS employs a combination of license-based authentication and user account management to control access to its simulation software. Unlike many modern web APIs that rely on tokens or OAuth, ITIS's methods are tailored to standalone or networked desktop applications.

The primary authentication methods include:

  • License File Authentication: This is the fundamental method for authorizing the use of ITIS software. Users receive a license file (e.g., .lic file) that contains cryptographic information validating their subscription or purchase. The software checks this file upon startup. These licenses can be node-locked (tied to a specific machine) or floating (managed by a license server for multiple users).
  • User Account Credentials: Within the software environments (e.g., Sim4Life, SEMCAD X), users typically create local profiles or accounts. These accounts manage user-specific settings, project histories, and potentially access to shared resources or cloud-based features if integrated. While not a primary authentication method for initial software access, they are crucial for personalized usage and data management.
  • Network License Server Authentication: For larger organizations, ITIS supports network license servers. Users authenticate against this central server, which then grants a license 'seat' to their client application. This method allows for flexible license management across a team or department.

The table below summarizes the primary authentication methods:

Method When to Use Security Level
License File Authentication Initial software installation, single-user deployments, node-locked licenses High (cryptographically signed, machine-specific)
User Account Credentials Personalized software usage, project management within the application Moderate (password-protected local accounts)
Network License Server Authentication Multi-user environments, corporate deployments, floating licenses High (centralized control, often integrated with enterprise identity systems)

Getting your credentials

Obtaining credentials for ITIS software involves a structured process that begins with purchasing or licensing the software. The specific steps depend on whether you are acquiring a new license or managing an existing one.

  1. Software Purchase/Licensing: The first step is to contact ITIS directly or an authorized distributor to license the software. During this process, you will specify your requirements (e.g., single-user, network license, specific modules).
  2. License File Generation: After purchase, ITIS will typically generate a unique license file for you. This often requires providing specific identifiers, such as the MAC address or host ID of the machine where the software will be installed (for node-locked licenses) or the server's details (for network licenses). Detailed instructions are provided in the ITIS Installation and Licensing Guide.
  3. License File Delivery: The license file is usually delivered via email or made available through a secure portal. You will need to download and install this file in a designated directory on your system or license server.
  4. Software Installation: Install the ITIS software (e.g., Sim4Life, SEMCAD X) on your machine. The installer will typically prompt you to locate the license file or configure the connection to a network license server.
  5. User Account Setup: Once the software is licensed and running, you may be prompted to create a local user profile or account within the application. This involves setting a username and password for accessing personalized features and saving project data.

For network license server setups, additional configuration steps are required, including installing and configuring the license server software on a dedicated machine. This server then manages and distributes licenses to client machines on the network. For enterprise environments, understanding Active Directory Domain Services or similar identity management systems can be beneficial for integrating license servers with existing IT infrastructure.

Authenticated request example

Given that ITIS products are primarily desktop-based simulation software rather than web APIs, the concept of an "authenticated request" differs significantly from typical HTTP requests. There are no direct API calls with authentication headers in the traditional sense. Instead, authentication occurs at the application level through license validation and internal user management.

An "authenticated request" in the context of ITIS software can be conceptualized as the successful launch and operation of the software after license validation. Here's a conceptual flow:

1. User launches Sim4Life application.
2. Sim4Life application checks for valid license file in designated directory (e.g., C:\ProgramData\IT'IS Foundation\Licenses).
3. If using a network license, Sim4Life attempts to connect to the configured license server (e.g., license-server.yourcompany.com:27000).
4. License server validates the client's request against available seats.
5. If a valid license is found/granted, Sim4Life proceeds to load.
6. User logs into their local Sim4Life user profile (if configured).
7. User can now access all licensed features and modules, e.g., open a new project, run an electromagnetic simulation.

This process is entirely handled by the client application and the underlying licensing mechanisms. There is no exposed API endpoint where a developer would send a programmatic request with an API key or OAuth token. The "request" is internal to the software's operation. For example, a user attempting to access a specific simulation module would implicitly be making an "authenticated request" to the software, which then verifies their license and user privileges to enable that functionality.

Security best practices

Ensuring the security of your ITIS software and associated data involves several best practices, particularly regarding license management, system security, and data handling.

1. Secure License File Storage:

  • Store license files in a secure location on your system, restricting access to authorized personnel only.
  • Avoid sharing license files indiscriminately, as they are tied to your software entitlement.
  • For network licenses, ensure the license server is protected with strong access controls and is regularly patched.

2. Strong User Account Management:

  • Use strong, unique passwords for any local user accounts within the ITIS software.
  • Implement regular password rotation policies.
  • If the software integrates with enterprise identity systems, leverage those systems' security features, such as multi-factor authentication (MFA), to protect user access.

3. System and Network Security:

  • Keep the operating system where ITIS software is installed updated with the latest security patches.
  • Employ robust antivirus and anti-malware solutions.
  • Configure firewalls to restrict network access to the license server and the machines running ITIS software, allowing only necessary ports and protocols.
  • Regularly back up your project data and license files to prevent data loss.

4. Data Handling and Privacy:

  • Be mindful of the sensitivity of the data you are simulating, especially in medical device safety evaluations.
  • Follow internal organizational policies for data classification and handling.
  • Ensure that simulation results and project files are stored in secure, access-controlled locations.

5. Software Updates:

  • Regularly update your ITIS software to the latest versions. Updates often include security enhancements and bug fixes that protect against known vulnerabilities.

Adhering to these practices helps maintain the integrity and confidentiality of your simulation work and ensures compliance with relevant security standards, such as those discussed by the W3C Web Security FAQ, even for non-web-based applications, by applying general principles of information security.