June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2521) Create a Security Guide

by B Long (JIRA)

[ https://issues.jboss.org/browse/TEIID-2521?page=com.atlassian.jira.plugin... ] B Long commented on TEIID-2521: ------------------------------- However, the reader is referred to https://community.jboss.org/wiki/CreatingACustomLoginModule which mentions configuration in "conf/login-config.xml" and "jboss-web.xml". Both of these should now be the server configuration file (e.g., standalone.xml or domain.xml), right? > Create a Security Guide > ----------------------- > > Key: TEIID-2521 > URL: https://issues.jboss.org/browse/TEIID-2521 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 8.4 > Reporter: B Long > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.4 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Create a Security Guide incorporating security sections from the Administrator's Guide and Developer's Guide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2521) Create a Security Guide

by B Long (JIRA)

[ https://issues.jboss.org/browse/TEIID-2521?page=com.atlassian.jira.plugin... ] B Long commented on TEIID-2521: ------------------------------- Looks good to me. Thank you for consolidating the Login Module setions. > Create a Security Guide > ----------------------- > > Key: TEIID-2521 > URL: https://issues.jboss.org/browse/TEIID-2521 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 8.4 > Reporter: B Long > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.4 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Create a Security Guide incorporating security sections from the Administrator's Guide and Developer's Guide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2519. --------------------------------- Resolution: Done Updated document with PK comment. I considered adding the message as WARNING, but since Odata metadata loads with every request (no-session affinity), it can really be verbose in the log file. so, I updated the error message to be more clear explaining the issue. https://docs.jboss.org/author/display/TEIID/OData+Support > Odata Table Query Not Workng > ---------------------------- > > Key: TEIID-2519 > URL: https://issues.jboss.org/browse/TEIID-2519 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3 > Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3. > Reporter: devin pinkston > Assignee: Ramesh Reddy > Priority: Minor > Labels: odata,, service,, web > Fix For: 8.4 > > Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml > > > When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found > When issuing the query: > http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries > We have also tried using: > http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries > When issuing the second query, this error is thrown: > <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error> > We can successfully display the metadata and see the details of the VDB by using: > http://localhost:8080/odata/Portfolio.1/$metadata > Please let me know if you need any more information -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2519) Odata Table Query Not Workng

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2519?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2519: ------------------------------------- Sorry, Devin. It is my mistake, I forgot to make note in the document about below. Since OData URL structure is dependent upon key structure, every table it exposes MUST either have a primary or unique key, otherwise they will be skipped during the metadata load. If the server is running in the DEBUG mode you would have seen a message in the log. When I was testing it, I used other VDB, it happens to be when I used the 8.3 Final I used the loopy VDB I supplied before and saw the behavior and thought it was a regression, however it is not, it is designed to work that way. So, make sure your tables have a PRIMARY KEY, and they will work. I will update the document with this info. > Odata Table Query Not Workng > ---------------------------- > > Key: TEIID-2519 > URL: https://issues.jboss.org/browse/TEIID-2519 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.3 > Environment: CentOS, JBOSS AS 7.1.1, Teiid 8.3. > Reporter: devin pinkston > Assignee: Ramesh Reddy > Priority: Minor > Labels: odata,, service,, web > Fix For: 8.4 > > Attachments: metadata.txt, portfolio-vdb.xml, portfolio-vdb.xml > > > When trying to query a table through Odata, a error is diplayed: EdmEntitySet refinedSalariesModel.refinedSalaries is not found > When issuing the query: > http://localhost:8080/odata/Portfolio.1/refinedSalariesModel.refinedSalaries > We have also tried using: > http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries > When issuing the second query, this error is thrown: > <error><code/><message lang="en-US">Could not find resource for relative : /refinedSalariesModel/refinedSalaries of full path: http://localhost:8080/odata/Portfolio.1/refinedSalariesModel/refinedSalaries</message></error> > We can successfully display the metadata and see the details of the VDB by using: > http://localhost:8080/odata/Portfolio.1/$metadata > Please let me know if you need any more information -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2513) Basic Auth with SSL Not Working for WS/OData Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2513?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2513. --------------------------------- Labels: CR2 (was: ) Resolution: Done Replaced the current http handling based on JDK calls with the WebClient class from the Apache CXF. This class uses "frontend-jaxrs" module which is not readily available in the AS7. This dependency has been added. with this change, now any HTTP based calls for REST based services use the above class, which can be configured similar to the SOAP based calls using the spring configuration file. This allows variety of support of authentication models like https, kerberos etc. See http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html > Basic Auth with SSL Not Working for WS/OData Translator > ------------------------------------------------------- > > Key: TEIID-2513 > URL: https://issues.jboss.org/browse/TEIID-2513 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.3 > Reporter: Ted Jones > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.4 > > > When connecting to an OData web service via SSL using basic auth, the connection fails. Per Ramesh, the keystore need to be configured with the proper cert for SSL. See http://stackoverflow.com/questions/6292799/basic-authentication-with-https -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013