October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-950) Add ability to control access to environment variables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins commented on TEIID-950: -------------------------------------- I already have the code ready for this, unless you've already done it? > Add ability to control access to environment variables > ------------------------------------------------------ > > Key: TEIID-950 > URL: https://jira.jboss.org/browse/TEIID-950 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Environment: Found by client on MMx 502, tested and found issue present through 551. > Reporter: Marc Shirley > Assignee: Ramesh Reddy > Fix For: 7.2 > > > SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-950) Add ability to control access to environment variables

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy reassigned TEIID-950: ---------------------------------- Assignee: Ramesh Reddy > Add ability to control access to environment variables > ------------------------------------------------------ > > Key: TEIID-950 > URL: https://jira.jboss.org/browse/TEIID-950 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Environment: Found by client on MMx 502, tested and found issue present through 551. > Reporter: Marc Shirley > Assignee: Ramesh Reddy > Fix For: 7.2 > > > SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-1242) teiid VDB inconsistent behavior

by Aleksandar Kostadinov (JIRA)

[ https://jira.jboss.org/browse/TEIID-1242?page=com.atlassian.jira.plugin.s... ] Aleksandar Kostadinov closed TEIID-1242. ---------------------------------------- > teiid VDB inconsistent behavior > ------------------------------- > > Key: TEIID-1242 > URL: https://jira.jboss.org/browse/TEIID-1242 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Environment: RHEL5, openjdk, SOA-P 5.1.0.dev3 > Reporter: Aleksandar Kostadinov > Assignee: Ramesh Reddy > Attachments: teiid-text-example.tgz > > > A dynamic VDB doesn't work properly on first server startup. One needs to restart server once to get a proper query result. > To reproduce: > cd jbossas/server > cp -a all dataservices > cd dataservices > unzip teiid-7.1.0.Final-jboss-dist.zip > tar xvfz teiid-text-example.tgz #see the file attached > 1. setup jbossas config with teiid and VDB > 2. start server > 3. connect & query => ERROR org.teiid.jdbc.TeiidSQLException: > Remote org.teiid.api.exception.query.QueryResolverException: interoperability does not exist. > 4. restart server > 5. connect & query => result retrieved > test query I used through adminshell: "SELECT fullname, price FROM (EXEC Interoperability.getTextFiles('Company.txt') ) AS ff, TEXTTABLE(ff.file COLUMNS symbol string, fullname string, price string) AS c" > When query is failing I see this in server log: > 05:00:18,225 WARN [PROCESSOR] Processing exception 'interoperability does not exist.' for request 87zeTL/KvEF6.0. Exception type org.teiid.api.exception.query.QueryResolverException thrown from org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-1242) teiid VDB inconsistent behavior

by Aleksandar Kostadinov (JIRA)

[ https://jira.jboss.org/browse/TEIID-1242?page=com.atlassian.jira.plugin.s... ] Aleksandar Kostadinov commented on TEIID-1242: ---------------------------------------------- Thanks for updating the query. Although I believe it was a real bug in dev2 build (because the same query worked after server restart) in ER1 and ER2 it is not present so will close the issue. > teiid VDB inconsistent behavior > ------------------------------- > > Key: TEIID-1242 > URL: https://jira.jboss.org/browse/TEIID-1242 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1 > Environment: RHEL5, openjdk, SOA-P 5.1.0.dev3 > Reporter: Aleksandar Kostadinov > Assignee: Ramesh Reddy > Attachments: teiid-text-example.tgz > > > A dynamic VDB doesn't work properly on first server startup. One needs to restart server once to get a proper query result. > To reproduce: > cd jbossas/server > cp -a all dataservices > cd dataservices > unzip teiid-7.1.0.Final-jboss-dist.zip > tar xvfz teiid-text-example.tgz #see the file attached > 1. setup jbossas config with teiid and VDB > 2. start server > 3. connect & query => ERROR org.teiid.jdbc.TeiidSQLException: > Remote org.teiid.api.exception.query.QueryResolverException: interoperability does not exist. > 4. restart server > 5. connect & query => result retrieved > test query I used through adminshell: "SELECT fullname, price FROM (EXEC Interoperability.getTextFiles('Company.txt') ) AS ff, TEXTTABLE(ff.file COLUMNS symbol string, fullname string, price string) AS c" > When query is failing I see this in server log: > 05:00:18,225 WARN [PROCESSOR] Processing exception 'interoperability does not exist.' for request 87zeTL/KvEF6.0. Exception type org.teiid.api.exception.query.QueryResolverException thrown from org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65). Enable more detailed logging to see the entire stacktrace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1245) exception trying to get a test connection through admin console to a text file based connection factory

by Aleksandar Kostadinov (JIRA)

exception trying to get a test connection through admin console to a text file based connection factory ------------------------------------------------------------------------------------------------------- Key: TEIID-1245 URL: https://jira.jboss.org/browse/TEIID-1245 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: RHEL5, openjdk, SOA-P 5.1dev3 Reporter: Aleksandar Kostadinov Assignee: Steven Hawkins Attachments: exception.txt I'm not completely sure there is a bug and if it is in teiid or admin console but it looks like a confusing behavior. When someone deploys a text file based connection factory like this attached to TEIID-1242 and without modifying login-config.xml, then trying to get a test connection results in an exception in the server log (see attached exception.txt). If login-config.xml is modified to have the "other" application policy be the same as the "soa" policy, then this error does not appear in the server log. I'm not sure where should policy name be configured but IMHO user should be able to perform admin console actions by default given she/he is logged in as admin to the console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1244) JBoss AS admin console troubles with text based connection factory

by Aleksandar Kostadinov (JIRA)

JBoss AS admin console troubles with text based connection factory ------------------------------------------------------------------ Key: TEIID-1244 URL: https://jira.jboss.org/browse/TEIID-1244 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: RHEL5, openjdk, SOA-P 5.1dev3 Reporter: Aleksandar Kostadinov Assignee: Steven Hawkins When one deploys a text file based connection factory some issues are present to the user trying to use admin console to look at it. Go to Resources -> Connection Factories -> No Tx ConnectionFactories -> TextFileDS -> Control Tab Clicking on "test connection" returns a result of "No". Also server log shows an exception (see attached exception.txt). Clicking on "List Statistics" for the first time results in an exception (see attached exception_listStatistics.txt). If user clicks on "flush", then consequent calls to list statistics are successful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
6
0 / 0

[JBoss JIRA] Commented: (TEIID-950) Add ability to control access to environment variables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins commented on TEIID-950: -------------------------------------- ENV('sessionid') returned the session id string. Presumably it was mainly for reporting. "SELECT ENV('sessionid'), ... " so that the client could record the id along with the results. There was little the user could do with it on the server side. > Add ability to control access to environment variables > ------------------------------------------------------ > > Key: TEIID-950 > URL: https://jira.jboss.org/browse/TEIID-950 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Environment: Found by client on MMx 502, tested and found issue present through 551. > Reporter: Marc Shirley > Fix For: 7.2 > > > SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-950) Add ability to control access to environment variables

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ] Ramesh Reddy commented on TEIID-950: ------------------------------------ How were ENV being used to get session_id currently? How would one use session_id in their queries? > Add ability to control access to environment variables > ------------------------------------------------------ > > Key: TEIID-950 > URL: https://jira.jboss.org/browse/TEIID-950 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Environment: Found by client on MMx 502, tested and found issue present through 551. > Reporter: Marc Shirley > Fix For: 7.2 > > > SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-950) Add ability to control access to environment variables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-950?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins commented on TEIID-950: -------------------------------------- It's been a while since this was looked at... I would now say there is little general utility in offering an env function. The only value that we specifically provide is the session id. So I think we could address this by adding a session_id system function and by adding a config property to enable the env function. It may even be a good idea to use a default of false. If there aren't any objections this could be done in 7.1.1. > Add ability to control access to environment variables > ------------------------------------------------------ > > Key: TEIID-950 > URL: https://jira.jboss.org/browse/TEIID-950 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Environment: Found by client on MMx 502, tested and found issue present through 551. > Reporter: Marc Shirley > Fix For: 7.2 > > > SELECT ENV('os.name') || ' ' || ENV('os.version') || ' ' || ENV('java.home') returns the details of the server, which from the client perspective is a security risk. This information is even visible by a user with no access to any tables. Client is looking to have this disabled, or have the ability to disable it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-245: --------------------------------- Fix Version/s: 7.3 (was: 7.2) pushing to 7.3 > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://jira.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.3 > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010