[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3553:
---------------------------------------
> I would categorize this as invalid usage.
It's not really invalid usage as we are allowing non-qualified names to be used. It's either something that we document about the v2 odata resolving or should change oreva to match Teiid's resolving and throw an exception.
> Odata - if table name is ambiguous, teiid returns result from first table
> -------------------------------------------------------------------------
>
> Key: TEIID-3553
> URL: https://issues.jboss.org/browse/TEIID-3553
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was allowed or denied
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3554:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Can you spell out a little more about what you want to see in the client exception (keeping in mind that only appropriate information can be exposed) and what should be in the audit log (keeping in mind that too larger volumes of information could need to be at lower more detailed logging levels).
> But I still think the role being applied is important so that if a user was setup incorrectly, it can easily be seen.
A user can have any number of roles, and any number of which can grant permission X - it only takes one. A role or roles not having a given permission is not considered an incorrect setup, but rather a design choice.
> Audit log is missing details related to what role was applied and what info was allowed or denied
> -------------------------------------------------------------------------------------------------
>
> Key: TEIID-3554
> URL: https://issues.jboss.org/browse/TEIID-3554
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: portfolioroles_data.xlsx
>
>
> Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data.
> Attaching excel file of the audit log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3553:
-------------------------------------
Yes, the ambiguity only exists in V2, because in V2, the $metadata can define multiple "schema" objects, and entity containers and only one of them can be set as default. When the schema name is not available it can be run against the default one. But in Teiid's implementation we have no default entity container is set, so it required that user uses the fully qualified name to access the entities.
In V4, there is only one schema and entity container for $metadata, but you can define references to other $metadata schemas in $metadata and use them with their fully qualified name in defining the relationships etc.
I would categorize this as invalid usage.
> Odata - if table name is ambiguous, teiid returns result from first table
> -------------------------------------------------------------------------
>
> Key: TEIID-3553
> URL: https://issues.jboss.org/browse/TEIID-3553
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3524:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1231050|https://bugzilla.redhat.com/show_bug.cgi?id=1231050] from NEW to MODIFIED
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2, 8.11
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was allowed or denied
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3554:
-------------------------------
Summary: Audit log is missing details related to what role was applied and what info was allowed or denied (was: Audit log is missing details related to what role was applied and what info was defined or allowed)
> Audit log is missing details related to what role was applied and what info was allowed or denied
> -------------------------------------------------------------------------------------------------
>
> Key: TEIID-3554
> URL: https://issues.jboss.org/browse/TEIID-3554
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: portfolioroles_data.xlsx
>
>
> Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data.
> Attaching excel file of the audit log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3524:
-------------------------------
Fix Version/s: 8.11
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2, 8.11
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3524) Database Logging not working
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3524.
--------------------------------
Resolution: Done
> Database Logging not working
> ----------------------------
>
> Key: TEIID-3524
> URL: https://issues.jboss.org/browse/TEIID-3524
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.7.1.6_2, 8.11
>
>
> When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db.
> I set up the logging as follows:
> Created java:/teiid-log-ds datasource.
> Added these to logging subsystem:
> {code:xml}
> <async-handler name="TEIID_COMMAND_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <async-handler name="TEIID_AUDIT_LOG">
> <level name="DEBUG"/>
> <queue-length value="50"/>
> <overflow-action value="block"/>
> <subhandlers>
> <handler name="TEIID_JPA_LOG"/>
> </subhandlers>
> </async-handler>
> <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions">
> <level name="DEBUG"/>
> </custom-handler>
> <logger category="org.teiid.COMMAND_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_COMMAND_LOG"/>
> </handlers>
> </logger>
> <logger category="org.teiid.AUDIT_LOG">
> <level name="DEBUG"/>
> <handlers>
> <handler name="TEIID_AUDIT_LOG"/>
> </handlers>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was defined or allowed
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3554:
------------------------------------
And even when an insert is tried, the client tool gets a good description:
Error: TEIID30492 Remote org.teiid.api.exception.query.QueryValidatorException: TEIID30492 User <teiidUser@teiid-security> is not entitled to action <CREATE> for 1 or more of the groups/elements/procedures.
SQLState: 50000
ErrorCode: 30492
And the audit does indicate a "denied" activity was applied. But I still think the role being applied is important so that if a user was setup incorrectly, it can easily be seen.
> Audit log is missing details related to what role was applied and what info was defined or allowed
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-3554
> URL: https://issues.jboss.org/browse/TEIID-3554
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: portfolioroles_data.xlsx
>
>
> Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data.
> Attaching excel file of the audit log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was defined or allowed
by Van Halbert (JIRA)
Van Halbert created TEIID-3554:
----------------------------------
Summary: Audit log is missing details related to what role was applied and what info was defined or allowed
Key: TEIID-3554
URL: https://issues.jboss.org/browse/TEIID-3554
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.1.6_2
Reporter: Van Halbert
Assignee: Steven Hawkins
Attachments: portfolioroles_data.xlsx
Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data.
Attaching excel file of the audit log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was defined or allowed
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-3554:
-------------------------------
Attachment: portfolioroles_data.xlsx
> Audit log is missing details related to what role was applied and what info was defined or allowed
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-3554
> URL: https://issues.jboss.org/browse/TEIID-3554
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: portfolioroles_data.xlsx
>
>
> Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data.
> Attaching excel file of the audit log data.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months