5.24.3.7.  Automatic Login

[Note]Note

The " Enable Automatic Login" option (plinkcommon.cfg -> [Login] block -> "AUTOLOGIN" key) no longer exists.

An (automatic) login works as follows:

  1. First, it is checked whether the user has already once logged in. The information on this can be found in $CADENAS_USER, in the token.db.

  2. If information from the last login is available there, it will be used.

  3. Otherwise, the application attempts to log in using the Windows login, but only if the " Windows " login method is enabled in the Permissions Management [Rights administration] section under User Databases [User databases].

  4. Otherwise, a login dialog with the enabled login methods is displayed.

  5. Regardless of this, you can open the " Authenticate User" [Authenticate user] or " Log In to Link Database [Log in to link database] " dialog box at any time from PARTdataManager / 3Dfindit.

    • PARTdataManager

    • 3Dfindit

Analysis of pappclient.cfg

The "applications" key no longer exists. It was removed because more and more applications are retrieving the SiteSetup via the app server, so it no longer makes sense to specify individual applications for this purpose. Either a computer has direct access to the directories (CADENAS_DATA, CADENAS_SETUP, CADENAS_SITESETUP, etc.) or it does not. In most cases, only one (admin) computer is needed on which settings are configured and catalogs are installed. In this case, it makes sense to use the CADENAS_APPSERVER variable to disable the RemoteFilesystem, the RemoteIndex, and the RemoteDatabase. The configuration options (parameters) for CADENAS_APPSERVER are described in Section 5.24.3.3, “ENTERPRISE 3Dfindit Client” documentation.

The Evaluation of the pappclient.cfg is as follows from:

  1. First, check whether a variable is set CADENAS_APPSERVER . If Yes, the pappclient.cfg is not evaluated, but all settings are pulled from the variable CADENAS_APPSERVER .

  2. Next, the system checks what should run on the app server:

    • remoteFileSystem: CADENAS_DATA is retrieved via the app server

    • remoteSetup or remoteSiteSetup: CADENAS_SETUP or CADENAS_SITESETUP runs on the app server

    • remoteDB: Database access is routed through the application server

    • remotepool: CADENAS_DATA/pool is accessed via the application server

  3. Distinction between local mode and remote mode ( clientmode key)

    • local

      In local mode, the app server is started by the client if it is not already running. In this mode, the " LocalApplications " key is evaluated. All applications specified there start the app server or connect to it. PARTadmin also starts an app server. The applications use the app server for searching.

      In local mode, PARTadmin always accesses the file system and the database directly. This means that the settings above are ignored.

    • remote

      In remote mode, all applications always access the AppServer.

      If the client application runs on the same computer as the application server, the following rule applies:

      • For PARTadmin: All settings ( remoteFileSystem, remoteSetup, remoteSiteSetup, remoteDB ) are ignored. Access always occurs directly.

      • All other applications: remoteFileSystem is ignored. The reason is that the application server launches applications such as psolupdater, which access CADENAS_DATA with write permissions.

    [Note]Note

    If catalogs are installed on a client using PARTadmin, you can use the CADENAS_APPSERVER variable to enable direct access to the data (by disabling remoteSetup and remoteSiteSetup).

    You can also configure these settings using the installation type "Local Software, Data, and Setup from an existing server [Software Local, data and setup from an existing server]."

    Software Local, data and setup from an existing server

    Software Local, data and setup from an existing server