April 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-28) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-28?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIIDSB-28: ------------------------------------- Component/s: core Assignee: Ramesh Reddy (was: Steven Hawkins) TEIID-5715 was resolved by adding the org.teiid.hiddenMetadataResolvable property [~rareddy] if you want more consistency across odata and the other access mechanisms, then we can set that system property or if you want it could be part of the EmbeddedConfiguration. > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIIDSB-28 > URL: https://issues.jboss.org/browse/TEIIDSB-28 > Project: Teiid Spring Boot > Issue Type: Quality Risk > Components: core > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.1.0 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5713) Safesforce-41 translator errors

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5713?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5713: ------------------------------------- [~shawkins] Since in the SB we are working with single classpath, what do you think how we should support scenarios like this where multiple same translator is available in multiple versions? > Safesforce-41 translator errors > ------------------------------- > > Key: TEIID-5713 > URL: https://issues.jboss.org/browse/TEIID-5713 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2, 11.2.3, 12.1.1 > > > Using the Salesforce-41 translator, just loading the metadata it fails with error. I have verified this with WF and SB. I think, it is probably better to switch this version to new version, and remove this version. > {code} > Caused by: com.sforce.ws.ConnectionException: ChangeEventHeader Not a valid enumeration for type: class com.sforce.soap.partner.SoapType > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:668) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556) > at com.force.api:41//com.sforce.soap.partner.Field.setSoapType(Field.java:1702) > at com.force.api:41//com.sforce.soap.partner.Field.loadFields1(Field.java:2039) > at com.force.api:41//com.sforce.soap.partner.Field.loadFields(Field.java:1912) > at com.force.api:41//com.sforce.soap.partner.Field.load(Field.java:1906) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readArray(TypeMapper.java:580) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:558) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.setFields(DescribeSObjectResult.java:398) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.loadFields1(DescribeSObjectResult.java:1421) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.loadFields(DescribeSObjectResult.java:1350) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectResult.load(DescribeSObjectResult.java:1344) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readArray(TypeMapper.java:580) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:558) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.setResult(DescribeSObjectsResponse_element.java:48) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.loadFields1(DescribeSObjectsResponse_element.java:107) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.loadFields(DescribeSObjectsResponse_element.java:83) > at com.force.api:41//com.sforce.soap.partner.DescribeSObjectsResponse_element.load(DescribeSObjectsResponse_element.java:77) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674) > at com.force.api:41//com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.bind(SoapConnection.java:180) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:154) > at com.force.api:41//com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:99) > at com.force.api:41//com.sforce.soap.partner.PartnerConnection.describeSObjects(PartnerConnection.java:1225) > at org.jboss.teiid.resource-adapter.salesforce-41@12.2.0-SNAPSHOT//org.teiid.resource.adapter.salesforce.SalesforceConnectionImpl.getObjectMetaData(SalesforceConnectionImpl.java:514) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5715) Option to not allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5715?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5715. ----------------------------------- Resolution: Done Add the system/env property org.teiid.hiddenMetadataResolvable (default true) to control whether hidden schema objects are directly resolvable. > Option to not allow hidden schema objects to be accessible > ---------------------------------------------------------- > > Key: TEIID-5715 > URL: https://issues.jboss.org/browse/TEIID-5715 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5715) Option to not allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5715?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5715: ---------------------------------- Component/s: Query Engine Fix Version/s: 12.2 Summary: Option to not allow hidden schema objects to be accessible (was: Don't allow hidden schema objects to be accessible) > Option to not allow hidden schema objects to be accessible > ---------------------------------------------------------- > > Key: TEIID-5715 > URL: https://issues.jboss.org/browse/TEIID-5715 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-65: ------------------------------------- Basically what we are talking about is what is the default behavior. My view is these conflicts may happen in 1% of situations. The user can always add a context to avoid conflicts. > It's that more of an issue of having a landing page? It is the service root. If one is copying and pasting this URL into fuse or any other application for integration purpose they need to know to add the "/odata4" otherwise it will end up in error. This should simply a little. > Also will you still need any of the /auth urls in standalone mode? We do not need any. Previous auth redirects are currently supported natively in Keycloak. > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5715) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5715?page=com.atlassian.jira.plugin... ] Steven Hawkins moved TEIIDSB-67 to TEIID-5715: ---------------------------------------------- Project: Teiid (was: Teiid Spring Boot) Key: TEIID-5715 (was: TEIIDSB-67) > Don't allow hidden schema objects to be accessible > -------------------------------------------------- > > Key: TEIID-5715 > URL: https://issues.jboss.org/browse/TEIID-5715 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > > To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-67) Don't allow hidden schema objects to be accessible

by Steven Hawkins (Jira)

Steven Hawkins created TEIIDSB-67: ------------------------------------- Summary: Don't allow hidden schema objects to be accessible Key: TEIIDSB-67 URL: https://issues.jboss.org/browse/TEIIDSB-67 Project: Teiid Spring Boot Issue Type: Quality Risk Reporter: Steven Hawkins Assignee: Steven Hawkins To be consistent with odata access hidden schema should not be accessible even over pg. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-66) User Undertow as web engine for OData

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-66: ----------------------------------- Summary: User Undertow as web engine for OData Key: TEIIDSB-66 URL: https://issues.jboss.org/browse/TEIIDSB-66 Project: Teiid Spring Boot Issue Type: Enhancement Components: OData Affects Versions: 1.0.2 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.1.0 Make the Undertow as the default web engine to be used with OData service -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIIDSB-65: --------------------------------------- > Simple root URL. Otherwise, we have to use something "/odata4" or "vdb-name". The user needs to be educated about it. That seems expected for odata users. Almost all example urls seem to contain one or more of odata, odata version, service or service name. > One that works with JPA model as well as the VDB based model If the convention adds /service or /project-name instead of /vdb-name that would still work. > In the OpenShift when the route is created you cannot create URL with context. That means clicking on it will end up in always a 404. It's that more of an issue of having a landing page? For example: https://services.odata.org/ > Perhaps we could move "static" to a more obscure name, such that chance of conflict is minimal? It would be best to limit the potential collisions to something that is definitely user chosen, such as the vdb / project name. Getting into the space of schema and entity names should be avoided if possible. Also will you still need any of the /auth urls in standalone mode? > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-65) OData include files are not being served correctly

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIIDSB-65?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIIDSB-65: ------------------------------------- There are a couple of reasons I kept the default at the root as service root. 1) Simple root URL. Otherwise, we have to use something "/odata4" or "vdb-name". The user needs to be educated about it. 2) One that works with JPA model as well as the VDB based model 3) In the OpenShift when the route is created you cannot create URL with context. That means clicking on it will end up in always a 404. Perhaps we could move "static" to a more obscure name, such that chance of conflict is minimal? > OData include files are not being served correctly > -------------------------------------------------- > > Key: TEIIDSB-65 > URL: https://issues.jboss.org/browse/TEIIDSB-65 > Project: Teiid Spring Boot > Issue Type: Bug > Components: OData > Affects Versions: 1.0.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 1.1.0 > > > The include metadata files are not being served correctly through OData interface. > One of the reference is calculated as http://rdbms-example-odata-teiid-dataservice.apps.garys-e21d.openshiftwor... > The class tries to request from this include url and this is what causes the 406 error > see $metadata int he URL -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2019