[TRAFODION-2395] Support conversion from secure to non-secure during installation

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: sql-security
• Assignee: Roberta Marton
• Reporter: Gao, Rui-Xian
• Created: 12/Dec/16 01:19
• Updated: 12/Dec/16 01:19

Description

If we enable ldap during the first install, security status is correct after the installation, and correct user/password can logon the database – This is correct.

*Problem 1 – If we install esgynDB again, and set the installation path same as the previous install, security will still be enabled though we gave ‘N’ to not to enable ldap during installation, and after installation, correct user/password can connect to the database.

*Problem 2 – if we install esgynDB again, set the installation path to a different directory, security will still be enabled though we gave ‘N’ to not to enable ldap during installation, and there will be internal error connecting to database since there is no config file under $MY_SQROOT/sql/scripts

output for problem#2, checking status after a second install –

[trafodion@suse-4 scripts]$ ./traf_authentication_setup --status
INFO: Start of security (authentication and authorization) script Thu Nov 24 11:30:09 CST 2016.

INFO: *** Trafodion security (authentication and authorization) status ***
Authentication is ENABLED
Authorization (grant/revoke) is ENABLED

INFO: End of security (authorization and authentication) script Thu Nov 24 11:30:14 CST 2016.
[trafodion@suse-4 scripts]$ trafci

Welcome to EsgynDB Enterprise Command Interface
Copyright (c) 2015-2016 Esgyn Corporation

Host Name/IP Address: suse-4.novalocal:23400
User Name: zz

• • • ERROR[8837] Invalid username or password. User: ZZ [2016-11-24 11:31:06]

User Name: trafodion
Password:

Role Name [Primary Role]:

• • • ERROR[29157] Server aborted abnormally or Connection timed out
    • ERROR[8837] Internal error occurred. User: TRAFODION [2016-11-24 11:31:15]