[JBoss JIRA] (TEIID-2485) Remove the resteasy patch thats no longer needed in EAP 6.1 ER5
by Van Halbert (JIRA)
Van Halbert created TEIID-2485:
----------------------------------
Summary: Remove the resteasy patch thats no longer needed in EAP 6.1 ER5
Key: TEIID-2485
URL: https://issues.jboss.org/browse/TEIID-2485
Project: Teiid
Issue Type: Task
Components: Build/Kits
Affects Versions: 8.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Fix For: 8.4
The resteasy patch thats provided in the kit is no longer needed. As of EAP 6.1 ER5, resteasy has been upgraded to 2.3.6, and resolves RESTEASY-812 issue.
I have verified the fix and have several EAP 6.1 ER5 servers running with Teiid 8.4 alpha without the patch applied.
--
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
11 years
[JBoss JIRA] (TEIID-2484) permission condition caching is incorrect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2484?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2484.
-----------------------------------
Resolution: Done
Addressed the three issues listed and added a check by the validator so that aggregate and other invalid functions produce a better error message.
A remaining issue is how/whether to apply row-based security during a matview load. The current behaviour is that the load will happen under the current user's roles. Other options are to disable row-based security for a mat view load, to throw an exception if filtering is applied during a load, or to do user scoped matviews (which doesn't seem feasible).
For internal matviews we can consistently apply the desired behaviour. However external matviews would seemingly require admin accounts as needed to by-pass the affect of row-based security if needed.
For now we'll just doc the current behaviour (which is somewhat consistent with for example if a source is applying row-based security and a mat view is loaded with an affected user).
> permission condition caching is incorrect
> -----------------------------------------
>
> Key: TEIID-2484
> URL: https://issues.jboss.org/browse/TEIID-2484
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.4
>
>
> The caching of permission conditions is being done across the whole of the roles, which will not be correct for other users with differing subsets of roles.
--
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
11 years
[JBoss JIRA] (TEIID-2484) permission condition caching is incorrect
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2484?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2484:
---------------------------------------
There are additional issues:
If an object has a permission, but no condition then an IllegalArgumentException will be thrown - the workaround is to use a "true" condition
If an object has conditions from multiple roles, the values are AND'd, not OR'd together - the workaround as with the original issue would be to only use conditions on a single role.
> permission condition caching is incorrect
> -----------------------------------------
>
> Key: TEIID-2484
> URL: https://issues.jboss.org/browse/TEIID-2484
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.4
>
>
> The caching of permission conditions is being done across the whole of the roles, which will not be correct for other users with differing subsets of roles.
--
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
11 years
[JBoss JIRA] (TEIID-2484) permission condition caching is incorrect
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2484:
-------------------------------------
Summary: permission condition caching is incorrect
Key: TEIID-2484
URL: https://issues.jboss.org/browse/TEIID-2484
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 8.4
The caching of permission conditions is being done across the whole of the roles, which will not be correct for other users with differing subsets of roles.
--
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
11 years
[JBoss JIRA] (TEIID-2483) Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2483:
----------------------------------
Fix Version/s: 8.4
> Error bring to connect to Teiid using 8.3 code in Designer against an 8.4 server
> --------------------------------------------------------------------------------
>
> Key: TEIID-2483
> URL: https://issues.jboss.org/browse/TEIID-2483
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.4
>
>
> This is the stacktrace I got when testing the connection to Van's new cluster at
> redhat-stl-eng3.usersys.redhat.com.
> org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1)
> at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658)
> at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575)
> at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136)
> at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29)
> at
> org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58)
> <snip>
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124)
> at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349)
> at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430)
> ... 48 more
--
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
11 years