You can install multiple instances of AuthMinder Server. However, you can use the Administration Console to configure the connection details to only one of these instances. This configured instance obtains the data of other instances for performing multi-instance management and failover from one instance to other for operations such as, configuration creation and credential issuance performed using Administration Console.
Note: In most cases of single-system deployments, you do not need to configure the instance. The default values will work out-of-the-box.
To specify the AuthMinder connectivity parameters:
|
Field |
Default Value |
Description |
|---|---|---|
|
IP Address of the AuthMinder Server |
localhost |
Enter the IP address of the system where you installed the required AuthMinder Server instance. Note: Ensure that the systems where AuthMinder components are installed are accessible to each other by their host name on the network. |
|
Port |
9743 |
Enter the port on which the Server Management web Service protocol service is exposed. Note: This field is valid only for Server Management Web Services protocol because it has to fetch information about other AuthMinder instances. |
|
Transport |
TCP |
Specify the transport mode for the corresponding component (Server Management Web Services, Administration Web Services, Transaction Web Services, and Authentication Native) to connect to the specified AuthMinder Server instance. The supported values are:
|
|
Server CA Certificate in PEM |
NA |
Upload the server certificate chain by using the respective Browse button in the corresponding field. Note: This field is applicable if SSL(1-Way) or SSL(2-Way) is selected in the Transport field. |
|
Client Certificate-Key Pair in PKCS#12 |
NA |
Upload the public and private key pair of the client certificate by using the respective Browse button in the corresponding field. Note: This field is applicable if SSL(2-Way) is selected in the Transport field. |
|
Client PKCS#12 Password |
NA |
The password corresponding to the P12 file. Note: This field is applicable if SSL(2-Way) is selected in the Transport field. |
|
Advanced Configurations Section |
||
|
Maximum Active Connections |
32 |
The maximum active connections that can be maintained between the client and the AuthMinder Server. |
|
Maximum Idle Connection |
8 |
The maximum number of idle connections that can be maintained with the AuthMinder Server. |
|
Maximum Wait Time (in Milliseconds) |
-1 |
The maximum amount of time (in milliseconds) the client must wait (when there are no available connections) for a connection to become available, before timing out. |
|
Minimum Wait Time for Eviction (in Milliseconds) |
300000 |
The minimum amount of time (in milliseconds) a connection might be idle in the pool before it is evicted by the idle connection evictor (if any). |
|
Time Between Eviction Runs (in Milliseconds) |
600000 |
The amount of time (in milliseconds) to wait before checking the pool to evict the idle connections. |
|
Connection Timeout |
10000 |
The maximum amount of time (in milliseconds) before the AuthMinder Server is considered unreachable. |
|
Read Timeout |
30000 |
The maximum amount of time (in milliseconds) allowed for a response from AuthMinder Server. |
Note: If you add a new AuthMinder Server instance, then before proceeding with the instance-specific configurations, click Save on this page. This ensures that the Administration Console gets the details of the newly added instance and the instance management functions will work smoothly for the newly added instance.
|
Copyright © 2013 CA.
All rights reserved.
|
|