[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
> One question is can multiple security-domains mapped to a single role?
They can now yes, but with the potential problem that the mapped role names are not specific to their respective security domains. In looking at EJB/Web JEE handling, they seem to assume just a single security domain.
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2761:
-------------------------------------
One question is can multiple security-domains mapped to a single role? Seems like that would be good to have to avoid duplication of roles in some scenarios.
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2810) Teiid doesn't support empty string when defining the jndi reference in the VDB
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2810?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2810.
-----------------------------------
Resolution: Rejected
This is expected. We are allowing JBoss logic to validate the service name. They don't allow empty.
> Teiid doesn't support empty string when defining the jndi reference in the VDB
> ------------------------------------------------------------------------------
>
> Key: TEIID-2810
> URL: https://issues.jboss.org/browse/TEIID-2810
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Teiid doesn't like when the jndi reference in the VDB is set to an empty space (example: connection-jndi-name=""). If I change it to " " (with space) its ok.
> This was also verified in Designer when setting the jndi name.
> The following warning is seen on the server:
> 08:04:19,487 WARN [org.teiid.RUNTIME] (MSC service thread 1-15) TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1: org.teiid.jboss.TeiidServiceNames$InvalidServiceNameException: TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1
> at org.teiid.jboss.TeiidServiceNames.dsListenerServiceName(TeiidServiceNames.java:96)
> but this will produce the following error message to the client when a query is executed:
> SELECT * FROM "YahooStocksXML_View"."YahooStocksXMLView"
> org.teiid.jdbc.TeiidSQLException: TEIID30504 YahooStocksXML_Source: org.jboss.as.naming.NamingContext is was not a ConnectionFactory implementation
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2810) Teiid doesn't support empty string when defining the jndi reference in the VDB
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2810?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2810:
------------------------------------
When the change is made, please support empty string and " " (space) as the same.
> Teiid doesn't support empty string when defining the jndi reference in the VDB
> ------------------------------------------------------------------------------
>
> Key: TEIID-2810
> URL: https://issues.jboss.org/browse/TEIID-2810
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Teiid doesn't like when the jndi reference in the VDB is set to an empty space (example: connection-jndi-name=""). If I change it to " " (with space) its ok.
> This was also verified in Designer when setting the jndi name.
> The following warning is seen on the server:
> 08:04:19,487 WARN [org.teiid.RUNTIME] (MSC service thread 1-15) TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1: org.teiid.jboss.TeiidServiceNames$InvalidServiceNameException: TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1
> at org.teiid.jboss.TeiidServiceNames.dsListenerServiceName(TeiidServiceNames.java:96)
> but this will produce the following error message to the client when a query is executed:
> SELECT * FROM "YahooStocksXML_View"."YahooStocksXMLView"
> org.teiid.jdbc.TeiidSQLException: TEIID30504 YahooStocksXML_Source: org.jboss.as.naming.NamingContext is was not a ConnectionFactory implementation
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2810) Teiid doesn't support empty string when defining the jndi reference in the VDB
by Van Halbert (JIRA)
Van Halbert created TEIID-2810:
----------------------------------
Summary: Teiid doesn't support empty string when defining the jndi reference in the VDB
Key: TEIID-2810
URL: https://issues.jboss.org/browse/TEIID-2810
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Teiid doesn't like when the jndi reference in the VDB is set to an empty space (example: connection-jndi-name=""). If I change it to " " (with space) its ok.
This was also verified in Designer when setting the jndi name.
The following warning is seen on the server:
08:04:19,487 WARN [org.teiid.RUNTIME] (MSC service thread 1-15) TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1: org.teiid.jboss.TeiidServiceNames$InvalidServiceNameException: TEIID50099 Invalid JNDI name "" specified in VDB Yahoo 1
at org.teiid.jboss.TeiidServiceNames.dsListenerServiceName(TeiidServiceNames.java:96)
but this will produce the following error message to the client when a query is executed:
SELECT * FROM "YahooStocksXML_View"."YahooStocksXMLView"
org.teiid.jdbc.TeiidSQLException: TEIID30504 YahooStocksXML_Source: org.jboss.as.naming.NamingContext is was not a ConnectionFactory implementation
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
Does it make more sense to allow the role (or vdb) to specify the applicable security domain? It seems like that would also be a valid mechanism:
{code}<data-role name='x' any-authenticated='true' security-domain='domain' grant-all='true'/>{code}
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2809) Support for property substitution in vdb.xml files
by Madhu Garimilla (JIRA)
Madhu Garimilla created TEIID-2809:
--------------------------------------
Summary: Support for property substitution in vdb.xml files
Key: TEIID-2809
URL: https://issues.jboss.org/browse/TEIID-2809
Project: Teiid
Issue Type: Enhancement
Affects Versions: 8.5
Environment: EAP 6.1 Alpha , Teiid 8.5
Reporter: Madhu Garimilla
Assignee: Steven Hawkins
I have created a vdb.xml where i have declared my translators in it. I would like to pass some parameters to one of my translators so that i do not need to change my vdb.xml whenever there is a change in value. These parameters derive the values from the system properties. So, i am using ${} notation to pass the value of the system properties to my translator. When i try to deploy my VDB and try to access the parameters inside the translator, These system properties are not being resolved to the actual values.
As per the thread https://community.jboss.org/thread/236325, this is not being supported as of now and requires an enhancement.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2785) Designer needs a way to utilize pushdown functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2785:
---------------------------------------
Added the boolean importer property importer.importPushdownFunctions to put the pushdown functions on the imported schema - they will still be under SYS as well at runtime, and the resolver will assume that the SYS form is preferred. This should be sufficient for Designer to use the DDL importer based upon the created metadata.
> Designer needs a way to utilize pushdown functions
> --------------------------------------------------
>
> Key: TEIID-2785
> URL: https://issues.jboss.org/browse/TEIID-2785
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> Pushdown functions, such as the ones exposed by the ModeShapeExecutionFactory, should be available at design time.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
grant-all should be handled as an attribute on a role. I'm not sure what the handling should be for the all in security domain. Seems like it will require a new collection on the data role. Another consideration is to have the role name mapping mechanism use a full form of role-name\@security-domain (similar to how we approach making user names specific to a security domain). Currently we don't specify what security domain a given mapped role is from, but it seems like this is probably a good idea in general. We could then just allow the role mapping \@security-domain to mean map to any user from that security domain.
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
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
10 years, 11 months
[JBoss JIRA] (TEIID-2761) Enable/disable transport per model/view/virtual procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2761:
----------------------------------
Comment: was deleted
(was: [English further down]
Geachte mevrouw, heer,
Van 18-1-2014 t/m 26-1-2014 ben ik afwezig. Uw mail wordt niet doorgezonden naar een collega. Voor dringende zaken kunt u contact opnemen met Jordan van Est van Ciber Nederland op telefoonnummer +31(0)40-2329090.
Dear Mrs. / Sir,
I am out of the office from 18-1-2014 untill 26-1-2014. Your mail is not forwarded to a colleague. For urgent matters you can contact Jordan van Est of Ciber Nederland on phone number +31(0)40-2329090.
Met vriendelijke groet / With kind regards,
Patrick Deenen
)
> Enable/disable transport per model/view/virtual procedure
> ---------------------------------------------------------
>
> Key: TEIID-2761
> URL: https://issues.jboss.org/browse/TEIID-2761
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.5
> Reporter: Patrick Deenen
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> It would be nice to be able to enable and disable access to models, tables, views or (virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
> One may want to have access to virtual procedures only by Odata for example.
--
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
10 years, 11 months