Security Provider Service
The Security Provider service enables you to manage security on the J2EE Engine.
This service runs on both the server and the dispatcher.
Server
Property |
Description |
Default Value |
MaxUsersCount |
The limit of concurrent security sessions on one cluster element. |
100000 |
SessionExpirationPeriod |
The default expiration period of newly created security sessions in milliseconds. |
100000000 |
SynchPermissionsWithDatabase |
Flag for synchronizing Java 2 security permissions with the configuration manager.
If this property is set to true, this does not reflect changes to the JavaPolicy file. Only the data base configuration is read. If you set the property to false, change the JavaPolicy file configuration and restart the service. The new configuration will be reflected on the server. |
true |
VerifyLoginModulesOnDeploy |
Flag for verifying login module declarations during deployment of components.
The deployment of an application with defined but not configured login modules will not pass if the property value is set to true. If you set it to false, the deployment of this application will pass and later you can manage the login modules configuration. |
true |
ServiceStartupLockAttemptsInterval |
Defines how many attempts to get a cluster-wide lock can be made during the first start up of the service. |
1000 |
ServiceStartupLockTimeLimit |
Defines the time interval between the attempts to get a cluster-wide lock during the first start up of the service in milliseconds. |
1800000 |
sessions_size |
Defines the size of the session pool. Measured in session numbers. |
200 |
LoginModuleClassLoaders |
Describes a list of libraries’ names that have to be used additionally for class loading a login module. The separator is comma (,).For example: “library:a,library:b” |
|
CheckForConsistentLogin |
When more than one login module in the authentication stack must succeed and verify the user’s identity, this property must be set to true.
If you have the BasicPasswordLoginModule in the stack, you must add to it the option StrictLogin=true, if the following conditions are met: ● The BasicPasswordLoginModule is one of the modules that must succeed. ● The BasicPasswordLoginModule is not the first login module that must succeed. More information: SAP Note 1269616. |
false |
