July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3035: --------------------------------------- I'm not sure of the flow entirely. Another of their pages implies they will pick up the current nt user if no credentials are set, but then the question is whether that is possible/appropriate. Otherwise if they are trying to flow thru with the login credentials or if there is some kind of ntlm token, that seems like it will require modifications on our part. Also it's not clear from the cxf pages if the necessary properties can be set via the config on the conduit or if they can only be set programatically. > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Debbie Steigner > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-3035: ---------------------------------------- I've already looked at that CXF page, would the customer then set the WS Datasource SecurityType config property to HTTPBasic? > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Debbie Steigner > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3035: ---------------------------------- Assignee: (was: Steven Hawkins) See https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+... That is all the support that is mentioned for CXF. > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Debbie Steigner > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3033: --------------------------------------- > So I can't recommend enabling it, because of this issue. I don't think there is a need to prevent Designer from exposing functionality that is essentially correct. > As for the change, just duplicate the JDBCMetadataProcessor for the ModeShapeMetadataProcessor No need to duplicate, there is already a subclass. > and make the change only for mode shape If you do so, then you need to make it an option. Otherwise what I'm getting at is that you are making the modeshape metadata idiosyncratic compared to the rest of the teiid importers. Just because Designer did it that way does not make it correct and I don't want the precedent to be that we have to mimic the Designer import logic moving forward in all cases as we convert more over to the Teiid connection importer. And again my qualm is the feature here is to "not quote identifiers", which is a general issue and not inherently specific to modeshape. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-3035: -------------------------------------- Summary: Request to add NTLM Security to Web service datasources Key: TEIID-3035 URL: https://issues.jboss.org/browse/TEIID-3035 Project: Teiid Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Misc. Connectors Reporter: Debbie Steigner Assignee: Steven Hawkins Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3033: ------------------------------------ The dynamic case for mode shape was really never used. Designer didn't allow you to use the Teiid Connection Importer, had to use the jdbc importer. And at this point, it hasn't been enabled. I was hoping to do what was planned, and that was move away from the JDBC importer to Teiid Connection importer. So I can't recommend enabling it, because of this issue. As for the change, just duplicate the JDBCMetadataProcessor for the ModeShapeMetadataProcessor and make the change only for mode shape. No need to impact any other translator. This is really specific to mode shape. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3033: --------------------------------------- I'm still not sure what change/fix is appropriate. The metadata that the modeshape translator is providing in a dynamic case has not changed in a number of releases. The only possibility for this to be viewed as a regression is from Designer's perspective. The next point is that name "simplifying" for Teiid table names is a general feature and not specific to modeshape. All of the teiid translators will report their metadata in the most straight-forward way possible. The only provision we have along these lines is that the MetadataFactory can automatically correct column names that contain a period. Otherwise there is no general routine - which would need to do quite a bit more than just replace semi-colon in the general case. So I'm interpreting this issue as desiring a name simplifier somewhere - either Teiid or Designer. Because you loose some of the ease of association with the source table name, introduce a greater chance for introducing name conflicts, etc., I haven't seen a need for that on the Teiid side. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-3033: ------------------------------------- I agree with Van. I guess you could call it a Designer regression, but not because of any source code regression. Even if Designer did customize the Teiid DDL Importer for the Modeshape translator .... the Dynamic VDB importer issue would still be there. Seems to me if you change/fix on the Teiid side, you kill 2 birds with one stone. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3033 at 7/15/14 4:17 PM: ------------------------------------------------------------- Its not a designer issue. The translator metadata processor will expose this usability issue if a dynamic VDB is used or the metadata is imported by obtaining the DDL from teiid (as designer does). I know, I wouldn't like having to quote everything in the query. was (Author: van.halbert): Its not a designer issue. The translator metadata processor will expose this usability issue if a dynamic VDB is used or the metadata is imported by obtaining the DDL from teiid (as designer does). > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-3033 at 7/15/14 4:16 PM: ------------------------------------------------------------- Its not a designer issue. The translator metadata processor will expose this usability issue if a dynamic VDB is used or the metadata is imported by obtaining the DDL from teiid (as designer does). was (Author: van.halbert): Its not a designer issue. The translator mete data processor will expose this usability issue if a dynamic VDB is used or the metadata is imported by obtaining the DDL from teiid (as designer does). > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2014