ADSS Admin Guide

Property

Description

OTP Configurations

Defines configurations related to OTP generated by the ADSS SAM:

• SAM_OTP_EXPIRY_TIME = 900 
  Time interval in seconds to define the expiry time of OTP sent to user device for authentication. Default value: 900
• SAM_OTP_LENGTH = 6
  Number of digits to define the total length of OTP. Possible values: 4,6 and 9. Default value: 6.

Request expiry period

Time interval in seconds to define the expiry period of authorised pending request. Default value: 120 

• SAM_REQUEST_EXPIRY_PERIOD = 120 

User authentication retries limit

This property is used to define the number of authentication attempts allowed on a user account for user password and OTPs. Default value: 5 

• SAM_USER_AUTH_RETRIES_LIMIT = 5

User block period

Time interval in seconds for which a user will be blocked by the SAM after its login retries limit or OTP retry limit reaches. Default value: 100

• SAM_USER_BLOCK_PERIOD = 100

SAD Format

Authorization request or SAD format while communicating with SAM Service. Possible values are JSON and XML. 
Default value: XML

• SAD_FORMAT = JSON

Verify trust on certificate import

If enabled, the user certificate and its chain will be verified and must be trusted up to the Registered CA via the Trust Manager. Ensure that the Issuing CA is registered in the Trust Manager with CA purpose for successful trust building. Default value: FALSE.

• VERIFY_TRUST_ON_CERT_IMPORT = FALSE

Note: Enabling this property will result in slow process of request because Certificate path validation and trust checking is an expensive process that’s why it will be disabled by default and will be used as per client needs.

Storing limited data into the database to minimize the database size

If your database size grows too quickly because a lot of SAM Service transactions are being logged, then the size of log information can be reduced by removing some data columns from the database logs. The following are the attributes which manages the logging of specified column:

• TRANSACTION_LOG_COLUMNS = 100 = ResponseStatus, RequestTime, ResponseTime, Request, Response, UserId, RelyingPartyId, RelyingPartyIp, RelyingPartySslCert, ErrorCode

Transaction logs settings

Transactions can be stored either directly or delayed for better performance. The following properties are used for logging:

• TRANSACTION_LOG_MODE = LAZY
  Used to decide whether the transactions are kept in memory before these are stored in the database (LAZY logging) or directly stored in the database (EAGER logging). Possible values: LAZY, EAGER
  In case of LAZY logging the transaction logs are kept in memory upto the number of seconds configured in TRANSACTION_LOG_LAZY_INTERVAL or number of transactions configured in TRANSACTION_LOG_LAZY_RECORD_COUNT whichever is reached first.
• TRANSACTION_LOG_LAZY_INTERVAL = 2
  When LAZY logging is configured, transactions are kept in memory upto the configured time or if the configured TRANSACTION_LOG_LAZY_RECORD_COUNT is reached before it.
• TRANSACTION_LOG_LAZY_RECORD_COUNT = 50
  When LAZY logging is configured, transactions are kept in memory until the configured number of transactions is reached or if the configured TRANSACTION_LOG_LAZY_INTERVAL is met before it.