January 2014 - teiid-issues - Jboss List Archives

[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 resolved TEIID-2761. ----------------------------------- Resolution: Done Added a grant-all option to a role and now allow the vdb property "security-domain" to specify what security domain is in use for the vdb. Users will not have to logon using the domain qualifier. This is useful in situations that previously would have required multiple security domains to be assigned to a given transport (we may even want to revisit that and just allow for the setting of a single default security domain). I did not add validation logic related to the security domain at deployment time as there didn't seem to be anything similar to that when defining the session service for a given transport. Added a release note and updated the reference as well. > 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2811) Accumulo RowID VARBINARY conversion

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2811?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2811. --------------------------------- Labels: Accumulo Alpha2 (was: Accumulo) Resolution: Done Modified to reading all the data as character based data when metadata is imported directly by the translator. The system default character encoding used to read and store this character based data, however user has choice to override it through translator override property if the encoding needs to be different. > Accumulo RowID VARBINARY conversion > ----------------------------------- > > Key: TEIID-2811 > URL: https://issues.jboss.org/browse/TEIID-2811 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Labels: Accumulo, Alpha2 > Fix For: 8.7 > > > Converting ROWID from byte to VARBINARY causes a metadata error. Switch to String to accomodate for handling other characters in the RowID. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2811) Accumulo RowID VARBINARY conversion

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2811?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2811: -------------------------------- Fix Version/s: 8.7 Assignee: Ramesh Reddy (was: Steven Hawkins) > Accumulo RowID VARBINARY conversion > ----------------------------------- > > Key: TEIID-2811 > URL: https://issues.jboss.org/browse/TEIID-2811 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Labels: Accumulo > Fix For: 8.7 > > > Converting ROWID from byte to VARBINARY causes a metadata error. Switch to String to accomodate for handling other characters in the RowID. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2811) Accumulo RowID VARBINARY conversion

by devin pinkston (JIRA)

devin pinkston created TEIID-2811: ------------------------------------- Summary: Accumulo RowID VARBINARY conversion Key: TEIID-2811 URL: https://issues.jboss.org/browse/TEIID-2811 Project: Teiid Issue Type: Bug Components: Connector API Affects Versions: 8.7 Reporter: devin pinkston Assignee: Steven Hawkins Converting ROWID from byte to VARBINARY causes a metadata error. Switch to String to accomodate for handling other characters in the RowID. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2806?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2806. --------------------------------- Resolution: Done Corrected the Authorizations to a central space and supported the null case too. > Accumulo Connector: Handling Authorizations with NULL value > ----------------------------------------------------------- > > Key: TEIID-2806 > URL: https://issues.jboss.org/browse/TEIID-2806 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Fix For: 8.7 > > > Currently the connector cannot handle null authorizations or roles left blank. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2806) Accumulo Connector: Handling Authorizations with NULL value

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2806?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2806: -------------------------------- Labels: Alpha2 (was: ) > Accumulo Connector: Handling Authorizations with NULL value > ----------------------------------------------------------- > > Key: TEIID-2806 > URL: https://issues.jboss.org/browse/TEIID-2806 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.7 > > > Currently the connector cannot handle null authorizations or roles left blank. -- 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

12 years, 2 months

1
0
0 / 0

[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: ------------------------------------- I have to clarify that when I say configured domain, not on transport but the security-domain it self. The only issue is usually the security domains get injected to session service at the start of the session service, in this case we need to do something else if the 'domainX' is not configured on the transport. It seems redundant to also define on transport but I am ok either way. > 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

12 years, 2 months

1
0
0 / 0

[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: ------------------------------------- Yes, that should be. This is effectively override of what defined on the transport then. If "domainX" is not a configured domain then should be error situation. > 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

12 years, 2 months

1
0
0 / 0

[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: --------------------------------------- > I do not think I follow what you mean here If a security domain is specified in a vdb.xml, e.g. as an attribute (or it could be a property): {code} <vdb name="x" version= "1" security-domain="domainX"> {code} Then for any access of that VDB we'll use domainX regardless of what is configured on the transport. > 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

12 years, 2 months

1
0
0 / 0

[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: ------------------------------------- > do we allow the vdb security domain to be the one that is used (the behavior I would expect) I do not think I follow what you mean here >would we require the vdb's security domain to be one of the one's configured on the transport. This is what I was saying to in previous comment to fail during the deployment if one not configured > 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

12 years, 2 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 January 2014