April 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-1550) Row level security enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1550. ----------------------------------- Labels: 7.4Beta3 (was: ) Fix Version/s: 7.4 Resolution: Done Added a getSubject method to the CommandContext and updated the role logic to check function access as well. > Row level security enhancements > ------------------------------- > > Key: TEIID-1550 > URL: https://issues.jboss.org/browse/TEIID-1550 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Labels: 7.4Beta3 > Fix For: 7.4 > > > Requesting Row level security model to restrict user access to sensitive information defining new Security Domain in SOA Platform configured to use XACML authorization. Specification of Business Rules that will restrict access to data at a row level based on User Profile attributes like cost center, roles, portfolio. > Currently this is not available for system or User Defined Functions, just tables. Requesting that this capability be added. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-1550) Row level security enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-1550: ------------------------------------- Assignee: Steven Hawkins > Row level security enhancements > ------------------------------- > > Key: TEIID-1550 > URL: https://issues.jboss.org/browse/TEIID-1550 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Labels: 7.4Beta3 > Fix For: 7.4 > > > Requesting Row level security model to restrict user access to sensitive information defining new Security Domain in SOA Platform configured to use XACML authorization. Specification of Business Rules that will restrict access to data at a row level based on User Profile attributes like cost center, roles, portfolio. > Currently this is not available for system or User Defined Functions, just tables. Requesting that this capability be added. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1491) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1491?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1491. --------------------------------- Resolution: Done With the latest changes from StatementImpl now JDBC query works fine using JDK1.5. May need to revise the release procedure to add this jar to the downloads. > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-1491 > URL: https://issues.jboss.org/browse/TEIID-1491 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 7.4 > > > The jdbc driver needs to support jdk 1.5 on the client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1557) Add support for retrieving generated keys

by Steven Hawkins (JIRA)

Add support for retrieving generated keys ----------------------------------------- Key: TEIID-1557 URL: https://issues.jboss.org/browse/TEIID-1557 Project: Teiid Issue Type: Feature Request Components: Connector API, JDBC Driver, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins We should add support for retrieving generated keys to support the JPA identity key generation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-1552) Error using EDS ODBC driver with Oracle OBEII tool to import metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1552?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-1552: ---------------------------------- Assignee: (was: Van Halbert) > Error using EDS ODBC driver with Oracle OBEII tool to import metadata > ---------------------------------------------------------------------- > > Key: TEIID-1552 > URL: https://issues.jboss.org/browse/TEIID-1552 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1 > Environment: Oracle OBIEE tool on windows, win 32 bit ODBC EDS driver > Reporter: Van Halbert > Priority: Critical > Attachments: obiee_error.txt > > > When using the Oracle OBIEE tool to import metadata from EDS using the EDS ODBC windows 32 bit driver, there is an exception when trying to view the column metadata for a table. See attachment for the exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1552) Error using EDS ODBC driver with Oracle OBEII tool to import metadata

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1552?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3022 to TEIID-1552: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1552 (was: SOA-3022) Affects Version/s: 7.1.1 (was: 5.1.0 GA) Component/s: ODBC (was: EDS) Security: (was: Public) > Error using EDS ODBC driver with Oracle OBEII tool to import metadata > ---------------------------------------------------------------------- > > Key: TEIID-1552 > URL: https://issues.jboss.org/browse/TEIID-1552 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1 > Environment: Oracle OBIEE tool on windows, win 32 bit ODBC EDS driver > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Attachments: obiee_error.txt > > > When using the Oracle OBIEE tool to import metadata from EDS using the EDS ODBC windows 32 bit driver, there is an exception when trying to view the column metadata for a table. See attachment for the exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1491) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1491?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-1491: -------------------------------- Fix Version/s: 7.4 Affects Version/s: 7.1.1 > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-1491 > URL: https://issues.jboss.org/browse/TEIID-1491 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 7.4 > > > The jdbc driver needs to support jdk 1.5 on the client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1550) Row level security enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ] Steven Hawkins moved SOA-3016 to TEIID-1550: -------------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1550 (was: SOA-3016) Component/s: Query Engine (was: Security) Security: (was: Public) > Row level security enhancements > ------------------------------- > > Key: TEIID-1550 > URL: https://issues.jboss.org/browse/TEIID-1550 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > > Requesting Row level security model to restrict user access to sensitive information defining new Security Domain in SOA Platform configured to use XACML authorization. Specification of Business Rules that will restrict access to data at a row level based on User Profile attributes like cost center, roles, portfolio. > Currently this is not available for system or User Defined Functions, just tables. Requesting that this capability be added. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1412) Teiid should take care of salesforce query limits by itself

by Wanja Pernath (JIRA)

Teiid should take care of salesforce query limits by itself ----------------------------------------------------------- Key: TEIID-1412 URL: https://issues.jboss.org/browse/TEIID-1412 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Affects Versions: 7.2, 7.1.1, 7.3 Environment: Teiid 7.1.1 on EAP 5.1 with CXF Reporter: Wanja Pernath Assignee: Steven Hawkins Salesforce has a query string limit of 10.000 chars. When Teiid is calculating and executing a query like this: SELECT Opportunity where AccountId in (a,b,c,d,e,f,g,h,i) It could extend the 10.000 chars limit of Salesforce. Right now teiid just stops with an Exception. Expected behavior is to have teiid splitting up the condition into correct portions and to execute the above query n times to circumvent the limit: SELECT Opportunity where AccountId in (a, b, c); SELECT Opportunity where AccountId in (d, e, f); SELECT Opportunity where AccountId in (g, h, i); -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
6
0 / 0

[JBoss JIRA] Closed: (TEIID-1437) It's not possible to deploy single file (*.xml) virtual database through web admin console

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1437?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1437. --------------------------------- > It's not possible to deploy single file (*.xml) virtual database through web admin console > ------------------------------------------------------------------------------------------ > > Key: TEIID-1437 > URL: https://issues.jboss.org/browse/TEIID-1437 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Affects Versions: 7.2 > Reporter: Robert Balent > Assignee: Ted Jones > Fix For: 7.4 > > > There are two ways how create virtual database. You can deploy *.vdb file which is basically zip archive with changed extension, or deploy just vdb.xml file. The second way doesn't work through soa admin console web interface. > Error message: > Failed to create Resource weather-vdb.xml - cause: Incorrect extension specified on filename > How to reproduce: > In soa web interface log in to Admin Console, than open "Virtual Database (VDB)s" link, than click "Add a new resource" button, and try to upload weather-vdb.xml which is attached. > Workaround: > Just copy weather-vdb.xml to the deploy folder. > weather-vdb.xml and weather-ds.xml which is required if you want to deploy vdb in active state are attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2011