gsk error 408 (GSK_ERROR_BAD_KEYFILE_PASSWORD)

gsk error 408 (GSK_ERROR_BAD_KEYFILE_PASSWORD) pops up in Plugin log file. Also, the configuration of webserver and inside the plugin config directory I don’t see any files being generated for plugin-sth or plugin-kdb.

Error message as seen in below screenshot,

IBM Support Portal has a technote mentioning the same here. Below text taken from IBM support site and is a perfect resolution for the steps.

1.Make sure the plugin-key.sth file exists in the actual directory listed in the preceding example. By default this plugin-key.sth file is created when SSL is enabled within WebSphere Application Server. If the Web server is remote, this file and the plugin-key.kdb file must be copied from the Application Server machine to the remote Web server machine in the directory specified in the preceding example.

2. If the file does exist, make sure the user account which the Web server is running under has read/execute permission to the plugin-key.sth. Also, it is possible that the plugin-key.sth file is corrupt or does not correspond with the existing plugin-key.kdb file. As a result, you must create a new plugin-key.sth file from the existing plugin-key.kdb file.

• Use the iKeyman GUI included with the IBM HTTP Server to open the plugin-key.kdb file. The password to open this file by default is WebAS (case sensitive).
• After you have the plugin-key.kdb file open, from the menu select: Key Database file > stash password. This creates a new plugin-key.sth file.

3. It is essential if there is an RDB (for example, plugin-key.rdb) and CRL (for example, plugin-key.crl) in the same directory as the plugin-key.kdb and plugin-key.sth file, remove these files from the directory.