Resolving invalid credential issue

Currently if a user profile contains invalid credentials and when an attempt is made to connect with this profile, the profile will be set into an 'invalid credential' status. Any internal request made to establish connection to this profile will also be rejected to avoid locking of this user account by the database server until the profile is updated with correct credentials.

Symptoms

In a customer environment, the invalid credential problem is usually temporary, or can be fixed very soon. But in DSM the admin has to manually validate the credentials to unlock this connection profile. 

Resolving the problem

The following two options are added in the configuration file dswebserver_override.properties,  to define DSM action when a connection profile contains invalid credentials.  

 dsweb_invalidCredentialsRetryTimes=3
 dsweb_invalidCredentialsIncrementalRetryInterval=15

The default value of dsweb_invalidCredentialsRetryTimes is 3.  The time unit of dsweb_invalidCredentialsIncrementalRetryInterval is minute and the default value is 15 minutes.

Note: the interval time is incremental, that is, if a connection fails due to an invalid credential issue, the Data Server Manager will retry after 15 minutes for the first time, then attempts the second time after 30 minutes, then attempts the third time after 45 minutes. Therefore after 90 minutes, the Data Server Manager will stop retrying to establish connection and will mark that specific connection profile as invalid. To unlock this connection profile, a connection profile owner must log in to Data Server Manager and edit it using a valid credential. This retry process will be stopped if the connection is successfully established in a single attempt or if the credential is updated during the process.

If the option dsweb_invalidCredentialsRetryTimes is not configured or assigned the value as 0, negative integers and non-integers, then the Data Server Manager will not attempt to establish connection to a database with invalid credential profile. In this situation, the second option dsweb_invalidCredentialsIncrementalRetryInterval will not be used.