You need to prepare additional inputs if you plan to augment AuthMinder’s standard authentication capability by implementing plug-ins, then you need to set the extra information that must be sent to AuthMinder Server in name-value pairs. AuthMinder’s com.arcot.webfort.common.api provides you the AdditionalInput class, which enables you to set this additional information that you plan to use.
Some of the pre-defined additional input parameters supported by the AdditionalInput class are:
Specifies the locale that AuthMinder will use in returning the messages back to the calling application.
This is useful in tracking transactions. You can use session ID or transaction ID for specifying this information.
Enables the TRACE logging for the transaction. The presence of the identifier irrespective of the value enables TRACE logging.
Used to control the log level for the transaction. The supported values are:
See appendix, "AuthMinder Logging" for more information on log levels.
Is used to indicate whether the sensitive data must be logged for the current transaction. For example, USERNAME of the user. The presence of the identifier irrespective of the value enables this logging.
Is used to indicate whether the database query execution has to be logged in detail. The presence of the identifier irrespective of the value enables this logging.
Specifies the transaction data that the end user enters in the Challenge field of the ArcotID OTP client to generate a passcode in the Sign mode. The maximum length of the signed data is 64 bytes. This implementation of the Transaction Signing feature conforms to the OATH Challenge-Response Algorithm (OCRA) as defined by RFC 6287.
|
Copyright © 2013 CA.
All rights reserved.
|
|