[
https://issues.apache.org/jira/browse/TRAFODION-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roberta Marton updated TRAFODION-1110:
--------------------------------------
Transferred as part of Launchpad - actually fixed as part of release 1.1
> LP Bug: 1438856 - Internal error returns during authentication after
> grant/revoke component priv
> ------------------------------------------------------------------------------------------------
>
> Key: TRAFODION-1110
> URL: https://issues.apache.org/jira/browse/TRAFODION-1110
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-security
> Reporter: Paul Low
> Assignee: Cliff Gray
> Priority: Blocker
> Fix For: 1.1 (pre-incubation)
>
>
> The following is returned during authentication for a valid user:
> *** ERROR[8837] Internal error occurred. User: TRAFODION
> This seems to happen after component privileges are granted/revoked in a
> previous session.
> To reproduce the problem you could do the following:
> Log on to the system as yourself, then switch to trafodion.
> Revoke the privilege in sqlci: revoke component privilege show on
> sql_operations from "PUBLIC";
> Try to connect through ODBC/JDBC from your client. The error should occur.
> More details can be found in email thread. I have not included it here since
> there are system info and passwords everywhere. Let me know if you need more
> details. Here is a summary:
> ... was again reporting internal errors on <cluster>. I really think this is
> because we authenticate as one user say <user1> and in next session try to
> access the metadata as that user ( even if it is for the same user <user1> or
> Trafodion ). This raises error 4481 leading to internal error.
> Should we be resetting the id back to DB__ROOT after each disconnect ? or is
> there some other solution ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
