About Client Authentication

The client authentication feature enables basic application server security by requiring that any client connecting to the SIMULIA Execution Engine supply credentials (e.g., user ID and password).

The credentials are verified against a security domain defined by the SIMULIA Execution Engine administrator. If the credentials pass the security check, the logon is allowed; otherwise, it is rejected. A client that passes this security check is said to be authenticated, which means that the identity of the client has been established.

A client is any program running on any computer in the network that attempts to contact the SIMULIA Execution Engine. SIMULIA Execution Engine clients include the Isight Design Gateway, SIMULIA Execution Engine stations, the SIMULIA Execution Engine Dashboard, and the SIMULIA Execution Engine Command Line Client. Each of these applications must provide valid user credentials to log on to the SIMULIA Execution Engine and to perform any SIMULIA Execution Engine-related operations.

Once a client has provided valid credentials and is authenticated, those credentials can be used to determine access to specific resources and information. All other SIMULIA Execution Engine security features are built upon the authenticated credentials, which is why enabling this feature is a prerequisite to all other SIMULIA Execution Engine security features.

Important: The WebLogic configuration template automatically configures the default security realm, myrealm, with the following global security roles: fiperuser, fiperstation, and fiperadmin. For more information, see About Security Roles.