September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3678) Unable to import native metada from HBase

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3678: ----------------------------------- Summary: Unable to import native metada from HBase Key: TEIID-3678 URL: https://issues.jboss.org/browse/TEIID-3678 Project: Teiid Issue Type: Bug Reporter: Juraj Duráni Assignee: Steven Hawkins Native metadata cloud not be imported if default values of import properties are used: {code:xml} <vdb name="hbase_test_vdb" version="1"> <model name="Source" type="PHYSICAL" visible="true"> <source name="Source" translator-name="hbase" connection-jndi-name="localHBase"/> <metadata type="NATIVE"/> </model> </vdb> {code} Exception: 09:08:06,722 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 2) JDBCMetadataProcessor - Importing tables 09:08:06,747 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 2) JDBCMetadataProcessor - Importing columns 09:08:06,748 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015865: Replaced deployment "test-vdb.xml" with deployment "test-vdb.xml" 09:08:06,782 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 2) JDBCMetadataProcessor - Importing primary keys 09:08:06,905 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 2) JDBCMetadataProcessor - Importing index info 09:08:06,906 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB hbase_test_vdb.1 model "Source" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed. Phoenix driver seems does not support unique indexes (https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/...) and returns every time the same ResultSet. After first table, Teiid closes it and next loop fails (https://github.com/teiid/teiid/blob/790e0da722de6f49685ce761302e54772843b...). The empty ResultSet is being used across all the PhoenixDatabaseMetaData class: getProcedures(...), getIndexes(...), getImportedKeys(...), getFunctions(...), ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3677) Update the Teiid Community Home Page to show all the types of data sources being supported

by Van Halbert (JIRA)

Van Halbert created TEIID-3677: ---------------------------------- Summary: Update the Teiid Community Home Page to show all the types of data sources being supported Key: TEIID-3677 URL: https://issues.jboss.org/browse/TEIID-3677 Project: Teiid Issue Type: Enhancement Components: Documentation Reporter: Van Halbert Assignee: Steven Hawkins With all the new types of data sources being supported by Teiid, it would be nice to indicate those on the Teiid Community home page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3618) Salesforce SSO using OAuth2 (RefreshToken, JWT)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3618?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3618. --------------------------------- Fix Version/s: 8.12 Resolution: Done Labels: Beta3 (was: ) Added support JWT based token propagation at the resource-adapter level. Verified with Salesforce. It is still a user exercise to make this work in true SSO fashion from Teiid. The issue there is Teiid login modules are more AD, LDAP which are password based, need to investigate how Teiid can participate or propagate these token through security context to the resource-adapter level. > Salesforce SSO using OAuth2 (RefreshToken, JWT) > ----------------------------------------------- > > Key: TEIID-3618 > URL: https://issues.jboss.org/browse/TEIID-3618 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Kenneth Peeples > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.12 > > > The current Salesforce Connector is using password+token for credentials. We should have the ability to use Salesforce SSO. > Implementation the same as described here (we could use Keycloak or Picketlink for IDP) - https://login.salesforce.com/help/pdfs/en/salesforce_single_sign_on.pdf? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3668) Support OAuth with JWT Bearer Access Token

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3668?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3668. --------------------------------- Fix Version/s: 8.12 Resolution: Done Labels: Beta3 (was: ) Added support JWT based token propagation at the resource-adapter level. Verified with Salesforce. It is still a user exercise to make this work in true SSO fashion from Teiid. The issue there is Teiid login modules are more AD, LDAP which are password based, need to investigate how Teiid can participate or propagate these token through security context to the resource-adapter level. > Support OAuth with JWT Bearer Access Token > ------------------------------------------ > > Key: TEIID-3668 > URL: https://issues.jboss.org/browse/TEIID-3668 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.12 > > > Support the OAuth JWT token propagation at web-service endpoints. Example flow with Salesforce defined here https://help.salesforce.com/HTViewHelpDoc?id=remoteaccess_oauth_jwt_flow.htm -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3676) Remove JwtBearerGrant CXF classes

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3676?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3676. --------------------------------- Resolution: Duplicate Issue > Remove JwtBearerGrant CXF classes > --------------------------------- > > Key: TEIID-3676 > URL: https://issues.jboss.org/browse/TEIID-3676 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.0 > > > When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3676) Remove JwtBearerGrant CXF classes

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3676: ----------------------------------- Summary: Remove JwtBearerGrant CXF classes Key: TEIID-3676 URL: https://issues.jboss.org/browse/TEIID-3676 Project: Teiid Issue Type: Task Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 9.0 When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3675) Remove JwtBearerGrant CXF classes

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3675: ----------------------------------- Summary: Remove JwtBearerGrant CXF classes Key: TEIID-3675 URL: https://issues.jboss.org/browse/TEIID-3675 Project: Teiid Issue Type: Task Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 9.0 When CXF version > 3.0.4 remove JwtBearerGrant related CXF classes, and use ones from CXF -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3618) Salesforce SSO using OAuth2 (RefreshToken, JWT)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3618?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3618: -------------------------------- Summary: Salesforce SSO using OAuth2 (RefreshToken, JWT) (was: Salesforce SSO) > Salesforce SSO using OAuth2 (RefreshToken, JWT) > ----------------------------------------------- > > Key: TEIID-3618 > URL: https://issues.jboss.org/browse/TEIID-3618 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Kenneth Peeples > Assignee: Ramesh Reddy > > The current Salesforce Connector is using password+token for credentials. We should have the ability to use Salesforce SSO. > Implementation the same as described here (we could use Keycloak or Picketlink for IDP) - https://login.salesforce.com/help/pdfs/en/salesforce_single_sign_on.pdf? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3618) Salesforce SSO

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3618?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3618: ------------------------------------- More helpful links https://developer.salesforce.com/blogs/developer-relations/2011/03/oauth-... https://help.salesforce.com/apex/HTViewHelpDoc?id=remoteaccess_oauth_jwt_... http://salesforce.stackexchange.com/questions/31904/how-and-when-does-a-s... http://salesforce.stackexchange.com/questions/30596/oauth-2-0-jwt-bearer-... http://salesforce.stackexchange.com/questions/88396/invalid-assertion-err... *OAuth Refresh Token Steps* 1) create connected app (may need to setup custom domain) 2) add profile and/or permissions set to the connected app 3) grab the "callback url" ( one need to set as https://localhost:443/_callback" 4) Run through the teiid-oauth-util.sh in "<eap>/bin" directory, use client_id, client_pass, and call back from connected app 5) use "https://login.salesforce.com/services/oauth2/authorize" authorize link 6) use "https://login.salesforce.com/services/oauth2/token" for access token url 7) the you get a refresh token from it 8) create a security-domain like {code} <security-domain name="oauth2-security"> <authentication> <login-module code="org.teiid.jboss.oauth.OAuth20LoginModule" flag="required" module="org.jboss.teiid.security"> <module-option name="client-id" value="xxxx"/> <module-option name="client-secret" value="xxxx"/> <module-option name="refresh-token" value="xxxx"/> <module-option name="access-token-uri" value="https://login.salesforce.com/services/oauth2/token"/> </login-module> </authentication> </security-domain> {code} *JWT based Steps* 1) Create a Self-Signed certificate locally or on Sales Force. (user->setup->security-controls->Certificate and Key Management) 2) Download the certificate and also put in keystore and download keystore. Keystore is needed for Teiid, certificate for the salesforce setup 3) Create connected app and select OAuth, and select all the scopes (some posts say refresh-token offline is must) 4) create a profile and/or permission set assign to the connected app. I believe before you can create a connected app you need to set up custom domain 5) When you creating connected app make sure you add the certificate in "Digital Certificate" 6) Now in Teiid create security-domain like {code} <security-domain name="oauth2-jwt-security"> <authentication> <login-module code="org.teiid.jboss.oauth.JWTBearerTokenLoginModule" flag="required" module="org.jboss.teiid.security"> <module-option name="client-id" value="xxxxx"/> <module-option name="client-secret" value="xxxx"/> <module-option name="access-token-uri" value="https://login.salesforce.com/services/oauth2/token"/> <module-option name="jwt-audience" value="https://login.salesforce.com"/> <module-option name="jwt-subject" value="your(a)sf-login.com"/> <module-option name="keystore-type" value="JKS"/> <module-option name="keystore-password" value="changeme"/> <module-option name="keystore-url" value="${jboss.server.config.dir}/salesforce.jks"/> <module-option name="certificate-alias" value="teiidtest"/> <module-option name="signature-algorithm-name" value="SHA256withRSA"/> </login-module> </authentication> </security-domain> {code} > Salesforce SSO > -------------- > > Key: TEIID-3618 > URL: https://issues.jboss.org/browse/TEIID-3618 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Reporter: Kenneth Peeples > Assignee: Ramesh Reddy > > The current Salesforce Connector is using password+token for credentials. We should have the ability to use Salesforce SSO. > Implementation the same as described here (we could use Keycloak or Picketlink for IDP) - https://login.salesforce.com/help/pdfs/en/salesforce_single_sign_on.pdf? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3553) Odata - if table name is ambiguous, teiid returns result from first table

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3553?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3553: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1234724|https://bugzilla.redhat.com/show_bug.cgi?id=1234724] from ON_QA to MODIFIED > Odata - if table name is ambiguous, teiid returns result from first table > ------------------------------------------------------------------------- > > Key: TEIID-3553 > URL: https://issues.jboss.org/browse/TEIID-3553 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12 > > > If table name is ambiguous, teiid returns data from first matching table. I expect, that it should return error message similar to exception which is thrown via JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2015