[JBoss JIRA] (TEIID-3431) replace bittronix in the examples with ironjacamar
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3431:
-------------------------------------
Summary: replace bittronix in the examples with ironjacamar
Key: TEIID-3431
URL: https://issues.jboss.org/browse/TEIID-3431
Project: Teiid
Issue Type: Quality Risk
Components: Embedded
Reporter: Steven Hawkins
Fix For: 8.11
The usage of bittronix in the examples should be replaced with jboss projects. This could be taken further to offer an embedded kit that includes transactionmanager functionality.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (TEIID-3425) Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3425?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3425:
-------------------------------------
Yes, we need to push out of 8.11 bucket for now.
> Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-3425
> URL: https://issues.jboss.org/browse/TEIID-3425
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: OS: Fedora 20
> java: IBM JDK 1.7
> arch: x86_64
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Attachments: set-up-mssql-ibm.cli, sql2012krb-static-vdb.xml, sql2012krb-vdb.xml
>
>
> I have configured a datasource for MSSQL database. The datasource uses PassthroughIdentityLoginModule. I have also created a VDB which requires kerberos authentication. I am trying to pass credentials used for authentication CLIENT <=> TEIID to datasource so they can be used for authentication TEIID <=> MSSQL.
> Method getConnection(..) (record in server log) is called with correct credentials, but SQLServerDriver throws an exception:
> initAuthInit failed privileged exception:-java.security.PrivilegedActionException: org.ietf.jgss.GSSException, major code: 13, minor code: 0
> major string: Invalid credentials
> minor string: Cannot get credential from JAAS Subject for principal: default principal
> Some ideas, but I am only guessing:
> 1. I have seen same exception (on client side) if system property "javax.security.auth.useSubjectCredsOnly" is set to false on client side. As this property is set to true in the server config (<property name="javax.security.auth.useSubjectCredsOnly" value="true"/>), it is probably not passed to the driver (or is being ignored).
> 2. SQLServerDriver sets two system properties by default (if no kerberos configuration file is specified) useDefaultCcache = true moduleBanner = false - see https://msdn.microsoft.com/en-us/library/gg558122%28v=sql.110%29.aspx - ibm kerberos login module will try to get TGT from ticket cache
> I have tried static kerberos configuration for same DS and there was no problem with it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (TEIID-3425) Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3425?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3425:
---------------------------------------
So we need to add a documentation note that these flows do not work for the IBM JDK. Should this and the IBM module issue be bucketed for 8.11 or a later release?
> Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-3425
> URL: https://issues.jboss.org/browse/TEIID-3425
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: OS: Fedora 20
> java: IBM JDK 1.7
> arch: x86_64
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Attachments: set-up-mssql-ibm.cli, sql2012krb-static-vdb.xml, sql2012krb-vdb.xml
>
>
> I have configured a datasource for MSSQL database. The datasource uses PassthroughIdentityLoginModule. I have also created a VDB which requires kerberos authentication. I am trying to pass credentials used for authentication CLIENT <=> TEIID to datasource so they can be used for authentication TEIID <=> MSSQL.
> Method getConnection(..) (record in server log) is called with correct credentials, but SQLServerDriver throws an exception:
> initAuthInit failed privileged exception:-java.security.PrivilegedActionException: org.ietf.jgss.GSSException, major code: 13, minor code: 0
> major string: Invalid credentials
> minor string: Cannot get credential from JAAS Subject for principal: default principal
> Some ideas, but I am only guessing:
> 1. I have seen same exception (on client side) if system property "javax.security.auth.useSubjectCredsOnly" is set to false on client side. As this property is set to true in the server config (<property name="javax.security.auth.useSubjectCredsOnly" value="true"/>), it is probably not passed to the driver (or is being ignored).
> 2. SQLServerDriver sets two system properties by default (if no kerberos configuration file is specified) useDefaultCcache = true moduleBanner = false - see https://msdn.microsoft.com/en-us/library/gg558122%28v=sql.110%29.aspx - ibm kerberos login module will try to get TGT from ticket cache
> I have tried static kerberos configuration for same DS and there was no problem with it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (TEIID-3425) Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3425?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3425:
-------------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Pass-through kerberos authentication on IBM JDK - principal is not passed to MSSQL driver
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-3425
> URL: https://issues.jboss.org/browse/TEIID-3425
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: OS: Fedora 20
> java: IBM JDK 1.7
> arch: x86_64
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Attachments: set-up-mssql-ibm.cli, sql2012krb-static-vdb.xml, sql2012krb-vdb.xml
>
>
> I have configured a datasource for MSSQL database. The datasource uses PassthroughIdentityLoginModule. I have also created a VDB which requires kerberos authentication. I am trying to pass credentials used for authentication CLIENT <=> TEIID to datasource so they can be used for authentication TEIID <=> MSSQL.
> Method getConnection(..) (record in server log) is called with correct credentials, but SQLServerDriver throws an exception:
> initAuthInit failed privileged exception:-java.security.PrivilegedActionException: org.ietf.jgss.GSSException, major code: 13, minor code: 0
> major string: Invalid credentials
> minor string: Cannot get credential from JAAS Subject for principal: default principal
> Some ideas, but I am only guessing:
> 1. I have seen same exception (on client side) if system property "javax.security.auth.useSubjectCredsOnly" is set to false on client side. As this property is set to true in the server config (<property name="javax.security.auth.useSubjectCredsOnly" value="true"/>), it is probably not passed to the driver (or is being ignored).
> 2. SQLServerDriver sets two system properties by default (if no kerberos configuration file is specified) useDefaultCcache = true moduleBanner = false - see https://msdn.microsoft.com/en-us/library/gg558122%28v=sql.110%29.aspx - ibm kerberos login module will try to get TGT from ticket cache
> I have tried static kerberos configuration for same DS and there was no problem with it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (TEIID-3429) Provide hooks to interrogate metadata prior to full import
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3429:
-------------------------------------
Summary: Provide hooks to interrogate metadata prior to full import
Key: TEIID-3429
URL: https://issues.jboss.org/browse/TEIID-3429
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
To support the Desinger we should offer the ability to interrogate metadata prior to full import.
Exploring metadata is effectively an entirely different mode of operation with respect to the current metadata processing logic on the Teiid side. Also partial metadata isn't something that would neatly be expressed through DDL - tables without columns, a list of schema names, etc.
Ways around that would be to expose source procedures for metadata interrogation:
getTableNames - which would probably give both the Teiid name and the name in source and consider the current translator metadata settings
getProcedureNames
And importer specific info such as for JDBC getTableTypes, getCatalogNames, getSchemaNames
I'd want to keep it fairly high level though. Getting column or key information I'd expect would be done through the normal full import.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (TEIID-3428) Data is being cleaned out after each server restart
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3428?page=com.atlassian.jira.plugin... ]
Van Halbert resolved TEIID-3428.
--------------------------------
Resolution: Done
> Data is being cleaned out after each server restart
> ---------------------------------------------------
>
> Key: TEIID-3428
> URL: https://issues.jboss.org/browse/TEIID-3428
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 6.2-8.7.2
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
> Fix For: 6.2-8.7.2, 8.11
>
>
> In the teiid-extensions logging persistence file, the schema is currently getting recreated after each restart due to being set to:
> <property name="hibernate.hbm2ddl.auto" value="create" />
> so it needs to change to be:
> <property name="hibernate.hbm2ddl.auto" value="update" />
> However, "update" isn't the ideal situation for production systems when DBA's like to restrict access as who can be creating tables. So they want the ddl script to run.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months