[JBoss JIRA] (TEIID-3075) OSGi bundle versions hardcoded
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3075?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3075:
--------------------------------
Assignee: (was: Ramesh Reddy)
> OSGi bundle versions hardcoded
> ------------------------------
>
> Key: TEIID-3075
> URL: https://issues.jboss.org/browse/TEIID-3075
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build/Kits
> Affects Versions: 8.7.1
> Reporter: Julian Coleman
> Priority: Minor
>
> The file:
> build/kits/karaf/teiid-karaf-features.xml
> contains hard-coded versions of some dependencies. For example:
> <bundle>wrap:mvn:org.apache.lucene/lucene-core/3.6.2</bundle>
> <bundle>mvn:org.infinispan/infinispan-query/5.2.1.Final</bundle>
> These should be replaced by the appropriate properties.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3059) Support consuming SOAP based service that is secured by Kerberos authentication
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3059?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3059:
-------------------------------------
After spending a ton of time and building a kerberos based example and trying to test with individual client and then through Teiid, the conclusion I derived is
1) To use any WS-Security features in "ws" translator, the resource-adapter must be configured with WSDL. When WSDL is configured it exposes all the methods on the port through dynamic metadata. These methods needs to be used instead of using generic "invoke" procedure. The reason for this is, the client proxy that gets generated through "Service.create()" call takes ws-policy information in the WSDL automatically. Otherwise the onerous is on the Teiid framework to do the same (through some duplicate config or WSDL) on generic Dispatch interface. Which seems cumbersome at best. The issue is current tooling is based on "invoke" based execution, this is need to be re thought when WSDL is available.
2) As per pass-through authentication for Kerberos token to the web service from logged in user, this feature just got committed to master branch in cxf (url in above comment), so when we move up in CXF version them we can support it. I tried to see if I can patch existing code, but the change involves CXF and WSS4J modules and totally trivial. So, I say we push this until we support later version of the CXF and WSS4J. (not in 2.0.1 of wss4j)
3) wrote sample examples here https://github.com/rareddy/ws-security-examples
4) I update documentation with above
> Support consuming SOAP based service that is secured by Kerberos authentication
> -------------------------------------------------------------------------------
>
> Key: TEIID-3059
> URL: https://issues.jboss.org/browse/TEIID-3059
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> CXF supports Kerberos based authentication in issuing a SOAP based web service call. This needs to be verified authentication scenario and further enhance code to support delegation of kerberos token.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3059) Support consuming SOAP based service that is secured by Kerberos authentication
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3059?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-3059 at 8/15/14 5:09 PM:
--------------------------------------------------------------
After spending a ton of time and building a kerberos based example and trying to test with individual client and then through Teiid, the conclusion I derived is
1) To use any WS-Security features in "ws" translator, the resource-adapter must be configured with WSDL. When WSDL is configured it exposes all the methods on the port through dynamic metadata. These methods needs to be used instead of using generic "invoke" procedure. The reason for this is, the client proxy that gets generated through "Service.create()" call takes ws-policy information in the WSDL automatically. Otherwise the onerous is on the Teiid framework to do the same (through some duplicate config or WSDL) on generic Dispatch interface. Which seems cumbersome at best. The issue is current tooling is based on "invoke" based execution, this is need to be re thought when WSDL is available.
2) As per pass-through authentication for Kerberos token to the web service from logged in user, this feature just got committed to master branch in cxf (url in above comment), so when we move up in CXF version them we can support it. I tried to see if I can patch existing code, but the change involves CXF and WSS4J modules and totally not trivial. So, I say we push this until we support later version of the CXF and WSS4J. (not in 2.0.1 of wss4j)
3) wrote sample examples here https://github.com/rareddy/ws-security-examples
4) I update documentation with above
was (Author: rareddy):
After spending a ton of time and building a kerberos based example and trying to test with individual client and then through Teiid, the conclusion I derived is
1) To use any WS-Security features in "ws" translator, the resource-adapter must be configured with WSDL. When WSDL is configured it exposes all the methods on the port through dynamic metadata. These methods needs to be used instead of using generic "invoke" procedure. The reason for this is, the client proxy that gets generated through "Service.create()" call takes ws-policy information in the WSDL automatically. Otherwise the onerous is on the Teiid framework to do the same (through some duplicate config or WSDL) on generic Dispatch interface. Which seems cumbersome at best. The issue is current tooling is based on "invoke" based execution, this is need to be re thought when WSDL is available.
2) As per pass-through authentication for Kerberos token to the web service from logged in user, this feature just got committed to master branch in cxf (url in above comment), so when we move up in CXF version them we can support it. I tried to see if I can patch existing code, but the change involves CXF and WSS4J modules and totally trivial. So, I say we push this until we support later version of the CXF and WSS4J. (not in 2.0.1 of wss4j)
3) wrote sample examples here https://github.com/rareddy/ws-security-examples
4) I update documentation with above
> Support consuming SOAP based service that is secured by Kerberos authentication
> -------------------------------------------------------------------------------
>
> Key: TEIID-3059
> URL: https://issues.jboss.org/browse/TEIID-3059
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> CXF supports Kerberos based authentication in issuing a SOAP based web service call. This needs to be verified authentication scenario and further enhance code to support delegation of kerberos token.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3044:
---------------------------------------
After the initial commit we have functions and functionparams system tables, however system and pushdown functions are not represented and function parameters have no uuids. FunctionParameter has been promoted to a more first class metadata object, but still needs refinement to be more usable (such as a property lookup via the system tables).
The next step will be to expose this info via databasemetadata.
> Add function metadata to system tables / databasemetadata
> ---------------------------------------------------------
>
> Key: TEIID-3044
> URL: https://issues.jboss.org/browse/TEIID-3044
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> We should expose source/system/udf functions via system metadata.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3080) incorrect foreign keys
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3080?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3080.
-----------------------------------
Resolution: Done
Removed the invalid foreign keys
> incorrect foreign keys
> ----------------------
>
> Key: TEIID-3080
> URL: https://issues.jboss.org/browse/TEIID-3080
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> With the broader introduction of array types the system tables for columns and procedure parameters with foreign keys to the datatype table are incorrect as there are no entries for the array types.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3044:
---------------------------------------
The next issue is that both system/translator functions and all function parameters are not created through a metadata factory so there is no proper way to set the datatype or a uuid. We'll need to come up with a consistent strategy though.
> Add function metadata to system tables / databasemetadata
> ---------------------------------------------------------
>
> Key: TEIID-3044
> URL: https://issues.jboss.org/browse/TEIID-3044
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JDBC Driver, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> We should expose source/system/udf functions via system metadata.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3081) Correct test errors with Java 8
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3081:
-------------------------------------
Summary: Correct test errors with Java 8
Key: TEIID-3081
URL: https://issues.jboss.org/browse/TEIID-3081
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Common
Affects Versions: 8.8
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
When running with a Java 8 vm there are test errors.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (TEIID-3080) incorrect foreign keys
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3080:
-------------------------------------
Summary: incorrect foreign keys
Key: TEIID-3080
URL: https://issues.jboss.org/browse/TEIID-3080
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Query Engine
Affects Versions: 8.5
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
With the broader introduction of array types the system tables for columns and procedure parameters with foreign keys to the datatype table are incorrect as there are no entries for the array types.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months