• No results found

DefaultServer Configuration

In document Fiori Configuration (Page 92-115)

3.4 Instance Management

3.4.1 DefaultServer Configuration

In the navigation tree, click the folder DefaultServer Configuration. The following screen appears.

3 Administration

Figure: Administration Console – Instance Management

To define the parameters which are described below, use the Edit button.

Entries marked with * are mandatory.

Option Details

Authentication Server Configuration

Login Module

Select the desired user authentication mechanism.

The following authentication mechanisms are available:

SPNegoLoginModule SecureLoginModuleLDAP SecureLoginModuleRADIUS SecureLoginModuleSAP BasicPasswordLoginModule

With the installation of Secure Login Server; Login Modules are installed in SAP NetWeaver. The name of the Login Modules is synchronized with the name of the JaasModule. The default is

SPNegoLoginModule.

For more information about the configuration of the Login Modules, see section 4.1 Configure Login Module.

Policy Configuration Name

This is the name of the configured login module stack.

Secure Login User CA Keystore

PseType

This parameter is read-only. The key store format is FilePSE.

PseName

Select the desired User CA for this instance.

User Certificate In this section, you define the Distinguished Name of

3 Administration

Configuration the user certificate will be defined. The common name (CN) is calculated by the Secure Login Server using the user credentials.

DN.country

Enter the country abbreviation in this field (C).

Example: DE DN.locality

Enter the regional information in this field (L).

Example: Walldorf DN.organization

Enter the company name in this field (O).

Example: Company xyz DN.organizationUnit

Enter the division of the company in this field (OU).

Example: SAP Security Department ValidityMinutes*

Time (in minutes) for which a user certificate is valid.

ValidityOffset*

Time offset in minutes relative to the server system time for the certificates to start being valid. This parameter is helpful if the client and server time are not in sync.

UseUPN

If the Microsoft user credentials are used and the User principal Name (UPN) is available, you can use this parameter to define whether the UPN is used in the CN field of the Distinguished Name of the user certificate.

Example:

If this parameter is configured with true, the CN field value is [email protected]

If this parameter is configured with false, the CN field value is CN=Username

Certificate Template Configuration

These parameters are read-only and display-only parameters used for generating user certificates. For more information, see section 3.3.5 Certificate Template

Log Configuration These parameters are read-only. For more information, see Instance Log Management.

Other Server Configuration LockDir

The path to which the lock file is saved. A lock file is created when the server encounters an internal error that requires manual intervention.

maxSessionInactiveInterval

Specifies the time, in seconds, between client requests before the servlet container will invalidate this session. This is applicable only in challenge-mode (for example, password change)

AdminServletHeader

Header text to be displayed on the status page.

Header text is used in Server Status and Instance Status.

AdminServletTrailer

Footer text to be displayed on the status page. Footer text is used in Server Status and Instance Status.

User-Defined Properties Any properties defined by the administrator are configured here.

WebClientKeyStoreType

Defines the certificate export format for the Secure Login Web Client. The default value is PKCS12.

For more information about possible parameters, see User-Defined Properties section.

Remember to configure the desired Login Module in SAP NetWeaver Administrator. For more information about the configuration of the Login Modules, see section 4.1 Configure Login Module.

User-Defined Properties

User-Defined Properties are used to define additional configuration issues depending on the instance. You can configure the following:

Secure Login Web Client Certificate Format

Certificate format used for Secure Login Web Client.

Certificate User Mapping Service

Change the value of the Common Name (CN) field of the user certificate Distinguished Name, based on the user mapping service.

Certificate User Name Service

Change the value format of the Common Name (CN) field of the user certificate Distinguished Name, based on the user name service.

Secure Login Web Client Certificate Format

Define the certificate export format for the Secure Login Web Client.

In default instance the default value is PKCS12. If you create a new instance is created, you need to define this parameter.

Certificate User Mapping Service

This section describes how to configure the use of an attribute from an LDAP or Microsoft Active Directory Server instead of the user name given by the client. This may be useful if the SAP user names and the authenticated user names (for example, from a Microsoft Windows domain) are not the same.

3 Administration

Example

The Microsoft user name is UserADS and the SAP user name is UserSAP. Without the Certificate User Mapping Service the Secure Login Server would create a user certificate with the Distinguished Name CN=UserADS.

If the SAP user name is stored in the Microsoft Active Directory, for example, in the attribute employeeID, the Secure Login Server can read this attribute and create a user certificate with the Distinguished Name CN=UserSAP.

This issue will be configured in the Certificate User Mapping Service.

The advantage of having the SAP user name in Distinguished Name is easier configuration in the SAP NetWeaver ABAP/JAVA Server environment (user mapping configuration).

If users change their own attributes (for example, through a self-service), and these attributes are used by the user certificate (issued by the Secure Login Server), a situation may occur in which these users are able to assign additional rights to themselves. Thus these users might get rights they are not supposed to have.

For this case, we recommend that you implement access restrictions for the change of user attributes.

An AS ABAP uses, for example, certificate-based logon with the users’ e-mail addresses in the Distinguished Names. The string in the certificate has the following format:

[email protected]

This means that the user’s e-mail address is used for the user mapping in SNC. If an administrator enables the user to change his or her own data, for example, e-mail

address, first name, last name etc. through a self-service, this user now has the possibility to enter, for example, his or her manager’s e-mail address ([email protected]) as attribute. Since this data is usually maintained centrally, this change would also affect the Secure Login Server. If the certification user mapping feature of the Secure Login Server is configured with the e-mail address as an attribute of the certificate, the user receives a certificate with the Distinguished Name [email protected]. This user is now able to log on to the AS ABAP as his or her manager.

The prerequisite is that the SAP user name is stored in the LDAP or Microsoft Active

Directory system. The Certificate User Mapping Service depends on the Secure Login Server user credential check against the authentication server.

Figure: Administration Console – User-Defined Properties Entries marked with * are mandatory.

Parameter Details

LdapReadServers* Number of LDAP servers that are configured here.

A numerical value is expected and must be 1 or higher. The given value is used as n to define an ordered list of servers that are called in a fail-over manner.

To disable all configured servers, leave this field empty.

LdapReadTimeoutn Connection timeout in seconds.

LdapReadUrln* The LDAP server to be used to retrieve that attribute LdapReadBaseDNn* Define the Base DN of the desired LDAP server

Example Microsoft Active Directory:

DC=DEMO,DC=LOCAL LdapReadDomainn* For Microsoft Active Directory:

LDAP domain to be appended to the given user name if it is not a User Principle Name. If the name is already in UPN format, the property is ignored.

LdapReadUsern* Define the technical user used to read the LDAP attribute from LDAP or Microsoft Active Directory Server.

Example: employeeID

LdapReadPassn* Define the password of the technical user used to read the LDAP attribute from LDAP or Microsoft Active Directory Server.

LdapReadAttributen* Define the LDAP attribute which is used for the common name (CN) of the user certificate Distinguished Name.

Example Microsoft Active Directory:

[email protected]

The value n in the parameter is a counter and is defined depending on the parameter LdapReadServers.

The Secure Login Server is able to verify user credentials and perform Certificate User Mapping on a different server. The prerequisite is that the user name is available on both servers.

Certificate User Name Service

3 Administration

There are two use cases available for configuring the Certificate User Name Service.

SAP user IDs have a maximum length of 12 characters (SAP NetWeaver ABAP environment), which needs to be considered by SNC X.509 certificates. The password length or value can be customized.

If user names in the common name (CN) field need a fixed or minimum length, padding can be turned on. Typically this configuration is used if personnel numbers are used.

SAP user IDs have a maximum length of 12 characters (SAP NetWeaver ABAP environment) which needs to be considered by SNC X.509 certificates. The password length or value can be customized.

Figure: Administration Console – User-Defined Properties

Parameter Details

MaxUserNameLength Maximum number of characters that a user name in the common name (CN) field can have. If the given user name is longer, it is cut from the right side.

Default value: 12 Example:

LongUsernameSAP is cut off to LongUsername with the default settings.

UserNamePaddingLength If user names in the common name (CN) field need a fixed or minimum length, padding can be turned on.

The padding length sets the minimum length of user names.

Default value: None

UserNamePaddingChar The padding character is used to fill user names on the left side if their size is smaller than the configured padding length (UserNamePaddingLength).

Default value: None Example:

UserNamePaddingLength = 11 and UserNamePaddingChar = 0.

The result is ShortName is extended to 00ShortName

Typically this configuration is used if personnel numbers are used.

Instance Configuration - Client Configuration

This section describes how you can define the client policy and how it is used by the Secure Login Client.

Client Policy

Define the URL of the Secure Login Server; used by the Secure Login Client to retrieve the client policy.

Figure: Administration Console – Instance Management - Client Policy Entries marked with * are mandatory.

Parameter Details

Policy URL* Network resource (Secure Login Server) from which the latest Secure Login Client policy can be

downloaded.

Policy URL depends on the instance configuration:

ClientPolicy.xml

Client Policy defined in the default instance of the Secure Login Server.

ClientPolicy.xml&path=000xx

Client Policy defined in instance xx (instance number) of the Secure Login Server.

PolicyTTL* Lifetime in minutes for verifying (update) a new client policy.

Default is 0 minutes.

By default, the Secure Login Client verifies a new client policy during the system startup of the client PC.

Network Timeout (seconds)*

Network timeout in seconds before the connection is closed if the server does not respond.

The default value is 45 seconds.

Disable update policy on startup

By default the Secure Login Client verifies during a new client policy during the system startup of the client PC.

You can use this parameter, to disable this feature.

3 Administration

No

Secure Login Client updates the client policy at startup.

Yes

Secure Login Client does not update the client policy at startup.

Default value is No.

Save Saves the configuration.

Cancel Cancels the configuration.

Applications

Defines which client profile is used for which SAP server application.

Figure: Administration Console – Instance Management - Applications

Parameter Details

Specify the application‟s action

Existing application profiles are handled as configured by action.

Clean

Deletes all existing profiles in the selected policy key before the given ones are written.

Replace

Replaces any existing profiles of the same name in the selected policy key with a given one.

Keep

Keeps any existing profiles of the same name in the selected policy does not write the given one (default).

The default value is Clean Add Application Adds new application Edit Edits the chosen application.

Delete Deletes the chosen application.

To define the application parameter, choose the Add Application or Edit button.

Figure: Administration Console – Instance Management – Edit Application Entries marked with * are mandatory.

Parameter Details

Application Name* Defines a name for this application template.

GSS Target Name* Application specific PSE URI (SAP Server SNC Name) that is matched when a suitable profile is searched. You can use the wildcards * and ?.

Examples:

SNC/CN=SAP, OU=SAP Security, C=DE SNC/CN=Server*, O=Company xyz

Using the value * means that the client profile is used for all SAP servers.

Profile The name of the client profile to be used for the desired application.

allowFavorite Allows the user to select the authentication profile manually in Secure Login Client.

No

A user cannot select the authentication profile manually in Secure Login Client.

Yes

A user can select the authentication profile manually in Secure Login Client.

The default value is Yes.

Save Saves the configuration.

Clear Clears fields (Application Name and GSS Target

3 Administration

Name).

Back Goes back to the Client Configuration page.

Profiles

This section describes the configuration of the client profile.

Figure: Administration Console – Instance Management - Profiles

Parameter Details

You can also specify the

profile‟s action Existing profiles are handled as configured by action.

Clean

Deletes all existing profiles in the selected policy key before the given ones are written.

Replace

Replaces any existing profiles of the same name in the selected policy key with a given one.

Keep

Keeps any existing profiles of the same name in the selected policy, does not write the given one (default).

The default value is Clean Add Profile Adds a new profile Edit Edits the chosen profile.

Delete Deletes the chosen profile.

To define the profile parameter, choose the Add Profile or Edit button.

Figure: Administration Console – Instance Management – Edit Profile Entries marked with * are mandatory.

Parameter Details

Profile Name* Defines a name for this profile template.

PSE Type Authentication type.

promptedlogin

Using this profile, the user is prompted to enter the user credentials.

windowslogin

Using this profile, the user credentials are provided automatically (only available for Microsoft Windows authentication with the SPNego login module).

The default value is windowslogin

Enroll URL* Secure Login Server URL that is used for user authentication and certificate request.

Enroll URL depends on the instance configuration.

<Server>/securelogin/PseServer

Enroll URL defined in the default instance of the Secure Login Server.

<Server>/securelogin/PseServer&id=000xx

Enroll URL defined in instance xx (instance number) of the Secure Login Server.

3 Administration

To configure further Enroll URLs, use the Add button.

This is the failover configuration for the Secure Login Client. If the Secure Login Client establishes a connection to the first Enroll URL, it tries the next Enroll URL, defined here.

HttpProxyURL HTTP proxy to be used with enrollment URLs. Only HTTP proxies without authentication and without SSL to proxy are supported.

Example: http://example.address.com:8888 Grace Period Value in seconds for the time in which an enrollment

is to be carried out before the certificate expires The default value is 0

InactivityTimeout Value in seconds until an automatic logout is performed (due to mouse and keyboard inactivity).

Possible values:

Value -1

No Single Sign-On (SSO). Each SNC connection forces a new login.

Value 0

No timeout. SSO without constraints.

The default value is 0.

Value n

Seconds until an automatic logout takes place.

Auto-Reenroll Attempts The number of successive failed authentications after which automatic re-enrollment is stopped.

You can activate the user name and password caching to ensure the automatic re-enrollment of certificates that are going to expire. Possible values:

0: Turn off:

Does not re-enroll automatically, does not cache user name and password. A re-enrollment must always be performed manually by the user.

>0 (n): Turn on with n tries to succeed:

Tries to re-enroll a maximum of n times before either a new certificate is received or the user name and password cache are cleared. The error counter is reset on success.

The default value is 0.

Key Size RSA Key Length.

The default value is 1024.

NewPinType Message text value used for messages (change PIN/password) to the Secure Login Client and Secure Login Web Client.

Available values are pin and password.

Unique Client ID Custom-defined string is displayed in the instance log or can be used for network filtering issues.

Network Timeout (seconds)

Network timeout (in seconds) before the connection is closed if the server does not respond

The default value is 45

Reauthentication This parameter defines how many logon attempts are permitted with the Secure Login Client logon form before it is closed again.

Example with the value 4:

The Secure Login Client offers the logon form 4 times (the logons fail, for example, due to wrong credential information) before the logon form is closed.

The default value is 0.

With this value, the logon form is never closed. The user needs to use the Cancel button to close the logon form.

SSL Host Common Name Check

This applies to the SSL Server certificate – this checks if the peer host name is given in the Common Name (CN) field of the SSL Server certificate.

True

Verifies the SSL server host name with the Common Name (CN) field of the SSL Server certificate.

False

Does not verify the SSL server host name with the Common Name (CN) field of the SSL Server certificate.

The default value is False SSL Host Alternative

Name Check

This applies to the SSL server certificate – this checks if the peer host name is given in the Subject Alternative Name attribute of the certificate.

True

Verifies the SSL server host name with the Subject Alternative Name attribute of the SSL Server certificate.

False

Does not verify the SSL server host name with the Subject Alternative Name attribute of the SSL Server certificate.

The default value is False

SSL Host Extension Check This applies to the SSL server certificate – this specifies whether the system checks if the extended key usage ServerAuthentication is defined.

True

Verify if the extended key usage ServerAuthentication is defined in the SSL server certificate.

False

Does not verify if the extended key usage

ServerAuthentication is defined in the SSL Server certificate.

The default value is False

User Warning MSIE Turns on/off a warning dialog box that appears after a new certificate has been propagated to the Microsoft

3 Administration

Crypto Store.

True

Turns on a warning dialog box.

False

Turns off a warning dialog box.

Note: Microsoft Internet Explorer must be restarted.

The default value is False

Auto-Enroll A user automatically gets an X.509 certificate when the Secure Login Client starts.

False: Turn off

True: Automatic provisioning of user certificates If pseType is set to windowslogin, user credentials are provided automatically (only applies for Microsoft Windows authentication).

If pseType is set to promptedlogin, the system prompts the users to enter their credentials.

Save Saves the configuration.

Clear Clears fields.

Cancel Cancels the configuration.

Download Files

This section describes how to download the relevant Client policy files for the Secure Login

This section describes how to download the relevant Client policy files for the Secure Login

In document Fiori Configuration (Page 92-115)