3DPassport

The 3DPassport service provides authentication and single sign-on (SSO) services for the whole 3DEXPERIENCE platform.

If your company already has an SSO system, 3DPassport can be configured as a replica to your enterprise solution, thus enabling SSO between your enterprise solution and the 3DEXPERIENCE platform.

There is no case in which an enterprise SSO solution can replace 3DPassport.

The following describes the 3DPassport service architecture:

The following prerequisites are required:

• OS: Redhat Enterprise Linux, Suse and Windows Server
• Database (configured to support UTF-8 and UTF-16): Oracle and SQL Server on both Windows Server and Linux
• Java Development Kit (JDK) / Apache TomEE+ are required. It is recommended to use an already installed one, but you can also install the embedded one for convenience.
• For the Reverse Proxy SSL and load balancing use Apache httpd or HA Proxy.

For more information about the prerequisites, see the Deployment: Strategic Platform Requirements: Server Hardware & Software section of the Program Directory.

Recommended memory size is 8GB RAM, or at least 4GB RAM and in this case set the java parameter Xmx=2GB in the setenv.sh/setenv.bat file.

As a general rule, 3DPassport should run with at least 4GB of dedicated memory. When 3DPassport is installed, only the Xms setting used to configure the JVM heap memory, is valued in the setenv.sh|.bat script used to launch the TomEE server.

To work properly, under normal load, 3DPassport needs to have at least 2GB of heap available. Since the Xmx setting is not set by default by installer, the rule that applies for the sizing of the heap is as follows: the maximum heap size will be 1/4 of the physical memory available. For example, if you install 3DPassport on a dedicated server with 8GB of RAM, the Xmx max heap size will be 2GB.

If 3DPassport is installed on a shared server alongside other applications (for example, 3DDashboard) deployed in another TomEE instance, it is preferable to set the Xmx value explicitly, at least to 2GB or more if possible, but it should not be more than half of the total memory available. For example, if you have only 4GB of dedicated memory available, Xmx should be set to 2GB as maximum.