September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-107: --------------------------------------- Summary: Update whoami operation to return authentication mechanism where verbose=true Key: WFCORE-107 URL: https://issues.jboss.org/browse/WFCORE-107 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha8 The admin console currently contains a "logout" handler that follows a round of HTTP message exchanges to trick the web browser into forgetting the credentials it has cached. This only makes sense where the browser has cached a credential - if we return the authentication mechanism then the console can make a better decision regarding displaying the logout link or could change the implementation so display a message to the user explaining why logout does not make sense. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-907) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-907?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-907: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: Awaiting Volunteers) I'm scheduling this, as I want to make sure it gets done in 9. > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFLY-907 > URL: https://issues.jboss.org/browse/WFLY-907 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Labels: rhq > Fix For: 9.0.0.CR1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-106) Enable GSSAPI/Kerberos Support for domain management over Remoting

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-106: --------------------------------------- Summary: Enable GSSAPI/Kerberos Support for domain management over Remoting Key: WFCORE-106 URL: https://issues.jboss.org/browse/WFCORE-106 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha8 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-105) Enable SPNEGO authentication for domain management over HTTP

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-105?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-105: ------------------------------------ Summary: Enable SPNEGO authentication for domain management over HTTP (was: Domain Management - Enable silent authentication using Kerberos) > Enable SPNEGO authentication for domain management over HTTP > ------------------------------------------------------------ > > Key: WFCORE-105 > URL: https://issues.jboss.org/browse/WFCORE-105 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Common_Authentication, Kerberos,, management_security, > Fix For: 1.0.0.Alpha8 > > > It should be possible for users to authenticate for domain management using Kerberos. > Over the HTTP interface this will be SPNEGO, for the Native connection we use SASL so can use GSSAPI -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-103) Add Full Kerberos Support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Darran Lofthouse moved WFLY-415 to WFCORE-103: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-103 (was: WFLY-415) Component/s: Domain Management Domain Management (was: Domain Management) (was: Security) Fix Version/s: 1.0.0.Alpha8 (was: 9.0.0.Beta1) > Add Full Kerberos Support > ------------------------- > > Key: WFCORE-103 > URL: https://issues.jboss.org/browse/WFCORE-103 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 1.0.0.Alpha8 > > > There are a number of steps required to full add Kerberos support - this is a top level tracking task to be resolved once all steps are complete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-907) Api returns internal server error instead of not found for non-existing path

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-907?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated WFLY-907: ---------------------------------- Assignee: (was: Darran Lofthouse) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFLY-907 > URL: https://issues.jboss.org/browse/WFLY-907 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Labels: rhq > Fix For: Awaiting Volunteers > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-907) Api returns internal server error instead of not found for non-existing path

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-907?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated WFLY-907: ---------------------------------- Fix Version/s: Awaiting Volunteers > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFLY-907 > URL: https://issues.jboss.org/browse/WFLY-907 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Darran Lofthouse > Labels: rhq > Fix For: Awaiting Volunteers > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-102) Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-102: --------------------------------------- Summary: Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback Key: WFCORE-102 URL: https://issues.jboss.org/browse/WFCORE-102 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.Beta1 The various base classes OSH authors use to create handlers force the author to deal with ServiceVerificationHandler and, during rollback, with removing any services the OSH added. This task is to have the OperationContext handle these things transparently, removing the need for authors to do so. To preserve compatibility, the various API methods authors may have overridden that expose the SVH and the list of added ServiceControllers will be retained (but deprecated), but the SVH and the list of handlers won't be used. The API javadoc will encourage use of method variants that don't use these parameters. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2515) JBAS014249 if a fire and forget asynchronous ejb call is made

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2515?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2515: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1030936|https://bugzilla.redhat.com/show_bug.cgi?id=1030936] from ASSIGNED to MODIFIED > JBAS014249 if a fire and forget asynchronous ejb call is made > ------------------------------------------------------------- > > Key: WFLY-2515 > URL: https://issues.jboss.org/browse/WFLY-2515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Beta1, 8.0.0.CR1 > Environment: Beta2 SNAPSHOT > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If an ejb method > @Asynchronous void fireAndForget(...) > is called remote and the client disconnect an Exception JBAS014249 will be thrown if the async method return. > {noformat} > ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014249: Error invoking method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname : java.lang.NullPointerException > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 11:30:20,242 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: org.jboss.remoting3.NotOpenException: Writes closed > at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:112) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:301) > at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:68) > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100) > ... 9 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3697) Custom http handlers support

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3697?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-3697: ----------------------------------- Backport PR https://github.com/wildfly/wildfly/pull/6713 > Custom http handlers support > ---------------------------- > > Key: WFLY-3697 > URL: https://issues.jboss.org/browse/WFLY-3697 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.2.0.CR1, 9.0.0.Alpha1 > > > We need support for custom handlers & filters > something along the lines > {code:xml} > <handlers> > <handler name="myhandler" class="full.class.name" module"full.module.name" /> > <handlers> > <filters> > <filter name="myfilter" class="full.class.name" module"full.module.name" /> > <filters> > {code} > There should also be a way to pass in arbitrary config options -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014