Authentication scope

Users module User menu / Configuration Authentication / Edit authentication scope

1. Authentication type


1.1. Authentication via Tomcat / Windows domain

With this setting, the user account that is used for logging in to the NT or ADS domain will also be used to log in to the portal. All users must be able to log in to their corresponding domains, or a position of trust must exist in regard to the domain of the Intrexx portal server.

Standard authentication (Plain text)

This option is required when users with browsers such as Netscape Navigator or Mozilla Firefox access the portal. These browsers support no encrypted login (integrated Windows authentication). The password will be transmitted in plain text in this case. Please note that the password may be intercepted with this unencrypted transmission method.

Also allow via HTTP (not secure)

If this option is activated, passwords will be transmitted unencrypted to the webserver.

Integrated Windows authentication

This option allows users with Microsoft Internet Explorer to login without entering a password. The users will be authenticated when they log on to Windows.

Domain

Enter the Windows domain you would like to log in to here.

Domain controller

Enter the Windows domain controller for the domain of your choice.

WINS server for name resolution

Enter the server that is responsible for WINS name resolution.

1.2. LDAP authentication

Server / Port

Specify the server and the port that should be used for the authentication in the Intrexx portal.

Authentication

Select the authentication method of your LDAP server. The Simple setting is the typical setting.

In an LDAP Bind Login three variables can be used, which will be expanded in runtime in the following order:

$[LOGIN_NAME] - Login name of the user
$[LOGIN_DOMAIN] - Login domain of the user
$[DN] - Distinguished Name of the user (usually entered via replication)

Click here for more information about LDAP authentication.

1.3. Intrexx authentication

Regardless of membership in local domains, each user will log in to the portal with the user name and the password from the User Manager. Select the user who will assume the role of anonymous user from the Anonymous user drop-down list. The anonymous user is the user who accesses the portal without logging on. This account will be used for all users before logging on. The type of authentication can be changed at a later point in time from Intrexx Authentication to Authentication via Web Server. The change will only take effect once the users are imported.

1.4. Generic authentication

Generic authentication allows the configuration of an authentication module for authentication via an LDAP server. In this case, the user name and the password will be transmitted in plain text. Please make sure that the login only is transferred via secure connections. To set up the generic authentication, please contact United Planet Consulting.

1.5. Other

Other authentication modules can be developed based on your needs. As examples, the authentication can be instituted here via X509 certificates, authentication to systems from third party providers, and so on. If you have questions, please contact United Planet Consulting.

1.6. Apply authentication type for all authentication scopes

The settings made here are applied to all other authentication scopes.