You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Gao, Rui-Xian (JIRA)" <ji...@apache.org> on 2017/01/25 14:43:26 UTC
[jira] [Commented] (TRAFODION-2411) connection aborted when
connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837839#comment-15837839 ]
Gao, Rui-Xian commented on TRAFODION-2411:
------------------------------------------
The fix has been verified on R2.2.1 rc1 -
User Name: trafodion
Password:
Role Name [Primary Role]:
Connected to EsgynDB Advanced
SQL>register user qauser1;
--- SQL operation complete.
SQL>connect qauser1/mypass;
Connected to EsgynDB Advanced
SQL>values(current_user);
(EXPR)
--------------------------------------------------------------------------------------------------------------------------------
QAUSER1
--- 1 row(s) selected.
SQL>disconnect;
Session Disconnected. Please connect to the database by using connect/reconnect command.
SQL>connect trafodion/traf123;
Connected to EsgynDB Advanced
SQL>unregister user qauser1;
--- SQL operation complete.
SQL>register user qauser1;
--- SQL operation complete.
SQL>connect qauser1/mypass;
Connected to EsgynDB Advanced
SQL>values(current_user);
(EXPR)
--------------------------------------------------------------------------------------------------------------------------------
QAUSER1
--- 1 row(s) selected.
> connection aborted when connecting with a re-registered user
> ------------------------------------------------------------
>
> Key: TRAFODION-2411
> URL: https://issues.apache.org/jira/browse/TRAFODION-2411
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-security
> Affects Versions: 2.2-incubating
> Reporter: Gao, Rui-Xian
> Assignee: Roberta Marton
>
> If we unregister a user and register again, then use the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT.
> [trafodion@gyvm-1 security]$ trafci
> Welcome to EsgynDB Enterprise Command Interface
> Copyright (c) 2015-2016 Esgyn Corporation
> Host Name/IP Address: gyvm-1.novalocal:23400
> User Name: zz
> *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15]
> User Name: trafodion
> Password:
> Role Name [Primary Role]:
> Connected to EsgynDB Advanced
> SQL>unregister user qauser10;
> --- SQL operation complete.
> SQL>register user qauser10;
> --- SQL operation complete.
> SQL>connect qauser10/mypasswd;
> Server aborted abnormally or Connection timed out
> *************************************************************************************
> it didn't quit, asked for host name, if we don't provide any info and hit Enter directly, then we will be back to the connection as DB__ROOT, so connecting with the re-registered user failed.
> *************************************************************************************
> Host Name/IP Address:
> Unknown Host:
> Host Name/IP Address:
> Unknown Host:
> SQL>select current_user from (values(1)) t;
> (EXPR)
> --------------------------------------------------------------------------------------------------------------------------------
> DB__ROOT
> --- 1 row(s) selected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)