[JBoss JIRA] (TEIIDDES-1738) Data role editor modifications can result in duplicate roles being generated.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1738?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1738:
----------------------------------------
DataRoleResolver.resolveDataRole() calls targetStillExists() for an object IPath. This method is returning FALSE for existing paths within a model. (i..e table) This is a bug and would result in permissions getting dropped.
> Data role editor modifications can result in duplicate roles being generated.
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1738
> URL: https://issues.jboss.org/browse/TEIIDDES-1738
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.7.3
> Environment: This appears to be more prominent on Windows, but duplicate roles have been observed on both Windows and Linux machines.
> Reporter: Marc Shirley
> Assignee: Johnathon Lee
>
> Editing the data roles through the VDB data roles editor can result in duplicate roles being generated, or the roles not being saved correctly in the current active copy of the role. Observed effects:
> 1) duplicate roles appearing
> 2) permissions being reset after VDB synchronization
> 3) duplicate roles appearing after attempting to delete a role
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1322) KRB5/GSSAPI Authentication support
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1322?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1322.
---------------------------------------
Resolution: Done
> KRB5/GSSAPI Authentication support
> ----------------------------------
>
> Key: TEIIDDES-1322
> URL: https://issues.jboss.org/browse/TEIIDDES-1322
> Project: Teiid Designer
> Issue Type: Feature Request
> Environment: Teiid Designer all versions
> Reporter: Graeme Gillies
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Hi,
> KRB5/GSSAPI authentication was added in Teiid Runtime 7.6 (see [1]) and this seems to work for both the JDBC and postgresql emulation layer.
> The problem is if you have a teiid instance secured by KRB5/GSSAPI and you wish to use the designer against it, you currently can't. This is because the "add teiid connection" screen takes a bunch of input and hand crafts the driver URL, which means you are unabled to add the extra jdbc url options needed such as
> authenticationType=KRB5;jaasName=Client;kerberosServicePrincipleName=demo(a)EXAMPLE.COM
> The add connection screen should be changed to either have a tick box to say "use gssapi authentication" and then allow you to specify the jaasName and kerberosServicePrincipalName, or it should have some way for you to add "custom jdbc url options" (or just allow you to manually craft the jdbc url).
> Regards,
> Graeme
> [1] https://issues.jboss.org/browse/TEIID-1610
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1322) KRB5/GSSAPI Authentication support
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1322?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1322:
-------------------------------------------
Url properties textbox added to wizard property page and is appended to the end of the url.
> KRB5/GSSAPI Authentication support
> ----------------------------------
>
> Key: TEIIDDES-1322
> URL: https://issues.jboss.org/browse/TEIIDDES-1322
> Project: Teiid Designer
> Issue Type: Feature Request
> Environment: Teiid Designer all versions
> Reporter: Graeme Gillies
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Hi,
> KRB5/GSSAPI authentication was added in Teiid Runtime 7.6 (see [1]) and this seems to work for both the JDBC and postgresql emulation layer.
> The problem is if you have a teiid instance secured by KRB5/GSSAPI and you wish to use the designer against it, you currently can't. This is because the "add teiid connection" screen takes a bunch of input and hand crafts the driver URL, which means you are unabled to add the extra jdbc url options needed such as
> authenticationType=KRB5;jaasName=Client;kerberosServicePrincipleName=demo(a)EXAMPLE.COM
> The add connection screen should be changed to either have a tick box to say "use gssapi authentication" and then allow you to specify the jaasName and kerberosServicePrincipalName, or it should have some way for you to add "custom jdbc url options" (or just allow you to manually craft the jdbc url).
> Regards,
> Graeme
> [1] https://issues.jboss.org/browse/TEIID-1610
--
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, 6 months
[JBoss JIRA] (TEIIDDES-879) Automtically create DTP Driver Definition based upon Teiid Runtime Configuration
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-879?page=com.atlassian.jira.plug... ]
Paul Richardson edited comment on TEIIDDES-879 at 6/20/13 5:54 PM:
-------------------------------------------------------------------
DTP driver instances provided for each version of Teiid runtime client installed. Each one configured with a jar entry pointing back to the client plugin, which provides the Teiid Driver as a JDBC 4 service.
was (Author: phantomjinx):
DTP driver instances provides for each version of Teiid runtime client installed. Each one configured with a jar entry pointing back to the client plugin, which provides the Teiid Driver as a JDBC 4 service.
> Automtically create DTP Driver Definition based upon Teiid Runtime Configuration
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-879
> URL: https://issues.jboss.org/browse/TEIIDDES-879
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Eclipse Integration
> Affects Versions: 7.1.1, 7.2, 7.3
> Reporter: Brian Fitzpatrick
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-879) Automtically create DTP Driver Definition based upon Teiid Runtime Configuration
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-879?page=com.atlassian.jira.plug... ]
Paul Richardson resolved TEIIDDES-879.
--------------------------------------
Resolution: Done
DTP driver instances provides for each version of Teiid runtime client installed. Each one configured with a jar entry pointing back to the client plugin, which provides the Teiid Driver as a JDBC 4 service.
> Automtically create DTP Driver Definition based upon Teiid Runtime Configuration
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-879
> URL: https://issues.jboss.org/browse/TEIIDDES-879
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Eclipse Integration
> Affects Versions: 7.1.1, 7.2, 7.3
> Reporter: Brian Fitzpatrick
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance.
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1738) Data role editor modifications can result in duplicate roles being generated.
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1738?page=com.atlassian.jira.plu... ]
Johnathon Lee reassigned TEIIDDES-1738:
---------------------------------------
Assignee: Johnathon Lee
> Data role editor modifications can result in duplicate roles being generated.
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1738
> URL: https://issues.jboss.org/browse/TEIIDDES-1738
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.7.3
> Environment: This appears to be more prominent on Windows, but duplicate roles have been observed on both Windows and Linux machines.
> Reporter: Marc Shirley
> Assignee: Johnathon Lee
>
> Editing the data roles through the VDB data roles editor can result in duplicate roles being generated, or the roles not being saved correctly in the current active copy of the role. Observed effects:
> 1) duplicate roles appearing
> 2) permissions being reset after VDB synchronization
> 3) duplicate roles appearing after attempting to delete a role
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1547) Cannot call web service which is created from model without primary key
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1547?page=com.atlassian.jira.plu... ]
Johnathon Lee commented on TEIIDDES-1547:
-----------------------------------------
Cool! Thanks for checking Ted.
> Cannot call web service which is created from model without primary key
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1547
> URL: https://issues.jboss.org/browse/TEIIDDES-1547
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 7.7.1
> Environment: JBDS 5.0.1
> Reporter: Eiichi Nagai
> Assignee: Ted Jones
> Fix For: 7.7
>
> Attachments: TEIIDDES-1547_reproducer.zip
>
>
> The web service which is created from model without primary key (or Access Pattern) cannot be called by the following exceptions.
> {noformat}
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1547) Cannot call web service which is created from model without primary key
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1547?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-1547.
---------------------------------
Resolution: Done
Resolved by fix in https://issues.jboss.org/browse/TEIIDDES-1498
> Cannot call web service which is created from model without primary key
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1547
> URL: https://issues.jboss.org/browse/TEIIDDES-1547
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 7.7.1
> Environment: JBDS 5.0.1
> Reporter: Eiichi Nagai
> Assignee: Ted Jones
> Fix For: 7.7
>
> Attachments: TEIIDDES-1547_reproducer.zip
>
>
> The web service which is created from model without primary key (or Access Pattern) cannot be called by the following exceptions.
> {noformat}
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
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, 6 months
[JBoss JIRA] (TEIIDDES-1687) Deploy VDB action gives no feedback when server is unavailable
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1687?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1687.
---------------------------------------
Resolution: Out of Date
Fixed by #1680 and #1688
> Deploy VDB action gives no feedback when server is unavailable
> --------------------------------------------------------------
>
> Key: TEIIDDES-1687
> URL: https://issues.jboss.org/browse/TEIIDDES-1687
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> The "Deploy VDB" action is enabled in Model Explorer context menu, but there is no feedback if you select it when server is not running.
> 1) The user should be shown a dialog, saying that no server is available.
> 2) When selecting the "Execute VDB" action, a dialog *is* shown - the Deploy action should do the same. The text on the Execute dialog needs some tweaking, though. Currently it says "Unable to establish connection to server 'admin'" - it should use the name of the server instead of 'admin'
--
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, 6 months