IBM Support

PH22098: UNIFIED CONSOLE LOGIN FAILS WITH ERRORCODE=-4214.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Users are unable to login into UC if the password contains a
    special character. The following error is returned:
    .
    HWCSEC0102E: The repository database for authentication is
    unavailable, Please contact the administrator or refer to log
    file for more details.
    .
    The log shows an invalid password error code -4214 was returned.
    .
    Nov 27, 2019 4:23:18 PM ERROR Error occured while establish JDBC
    connections [jcc][t4][2013][11249][4.24.92] Connection
    authorization failure occurred. Reason: User ID or Password
    invalid. ERRORCODE=-4214, SQLSTATE=28000
    com.ibm.db2.jcc.am.SqlInvalidAuthorizationSpecException:
    [jcc][t4][2013][11249][4.24.92] Connection authorization failure
    occurred. Reason: User ID or Password invalid. ERRORCODE=-4214,
    SQLSTATE=28000
    .
    The problem occurs because the script that encrypts the password
    (which is then stored in the metadb.properties file) does not
    handle special characters unless the password is enclosed in
    single quotes.  For example, if the password is "abcdef$ghijkl",
    the crypt.sh script appears to truncate the password at the $
    character.
    .
    [root@savoy1 bin]# ./crypt.sh abcdef$ghijkl
    wtiv2_ed86de04dbc58a927cbbcd64d1192585
    .
    [root@savoy1 bin]# ./crypt.sh abcdef
    wtiv2_ed86de04dbc58a927cbbcd64d1192585
    .
    If the password is delimited with single quotes, the encryption
    is correct.
    .
    [root@savoy1 bin]# ./crypt.sh 'abcdef$ghijkl'
    wtiv2_5de632c6b08efbe4ad6a0b6900875b18
    .
    Because the wrong encrypted password is stored in the
    metadb.properties file, the login fails.
    

Local fix

  • Manually encrypt the password using the
    /usr/ibmpacks/bigsql-uc/6.0.0.0/ibm-datasrvrmgr/dsutil/bin/crypt
    .sh script with the password enclosed in single quotes, as in
    the above example.  Update the
    /usr/ibmpacks/bigsql-uc/6.0.0.0/ibm-datasrvrmgr/Config/metadb.pr
    operties file with the correctly encrypted password. then
    restart UC from the command line (not through Ambari).
    

Problem summary

  • Please see problem discription.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH22098

  • Reported component name

    IBM BIG SQL

  • Reported component ID

    5737E7400

  • Reported release

    600

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-11

  • Closed date

    2020-09-09

  • Last modified date

    2020-09-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"600"}]

Document Information

Modified date:
10 September 2020