August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBASMP-62) Add non blocking exception patterns on Command execution

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-62?page=com.atlassian.jira.plugin.... ] James Perkins updated JBASMP-62: -------------------------------- Fix Version/s: (was: 7.6.Final) > Add non blocking exception patterns on Command execution > -------------------------------------------------------- > > Key: JBASMP-62 > URL: https://issues.jboss.org/browse/JBASMP-62 > Project: JBoss AS Maven Plugins > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: wildfly > Affects Versions: 7.6.Final > Reporter: Steve Favez > Assignee: James Perkins > > When a command execution returns an error, it's not possible to continue (in the end, the build fails). So, for example, if you execute a "module add" command for each "predeploy" on a jboss:run, it won't work the second time. It could be good to have an attribute in the command allowing to pass an "acceptable exception pattern" (for example - Module com.oracle already exists) - that won't block commands list execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-854) Fallback to FORM authentication when an invalid kerberos token is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-854?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-854: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131225, https://bugzilla.redhat.com/show_bug.cgi?id=1131229, https://bugzilla.redhat.com/show_bug.cgi?id=1133098 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1131225) > Fallback to FORM authentication when an invalid kerberos token is used > ---------------------------------------------------------------------- > > Key: SECURITY-854 > URL: https://issues.jboss.org/browse/SECURITY-854 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_4_Final > > > Negotiation will not fallback to FORM authentication if the client has a kerberos token from a different KDC than what JBoss is configured to use. > This results in the user getting presented with a 401 error and no way to login. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-854) Fallback to FORM authentication when an invalid kerberos token is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-854?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-854: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1131225, https://bugzilla.redhat.com/show_bug.cgi?id=1131229, https://bugzilla.redhat.com/show_bug.cgi?id=1133098, https://bugzilla.redhat.com/show_bug.cgi?id=1133099 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1131225, https://bugzilla.redhat.com/show_bug.cgi?id=1131229, https://bugzilla.redhat.com/show_bug.cgi?id=1133098) > Fallback to FORM authentication when an invalid kerberos token is used > ---------------------------------------------------------------------- > > Key: SECURITY-854 > URL: https://issues.jboss.org/browse/SECURITY-854 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_4_Final > > > Negotiation will not fallback to FORM authentication if the client has a kerberos token from a different KDC than what JBoss is configured to use. > This results in the user getting presented with a 401 error and no way to login. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2996) Remove need for native-interface on the Host Controller

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2996?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-2996: -------------------------------------- Assignee: Emmanuel Hugonnet (was: Brian Stansberry) > Remove need for native-interface on the Host Controller > ------------------------------------------------------- > > Key: WFLY-2996 > URL: https://issues.jboss.org/browse/WFLY-2996 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.CR1 > > > The HC requires a native-interface because the intra-domain comms (slave->master and server->HC) are hard coded to the "remote" protocol. Make this configurable for slave->master and dynamically determine what to use for server->HC. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3574) management API blocking write requests during initialization

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3574?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-3574. ------------------------------------ Resolution: Won't Fix > management API blocking write requests during initialization > ------------------------------------------------------------ > > Key: WFLY-3574 > URL: https://issues.jboss.org/browse/WFLY-3574 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.Final > Environment: default configuration > Reporter: Michael Mutschler > Assignee: Brian Stansberry > > I want to apply some configuration before the real application is starting. Mainly I want to update a datasource. Therefore I wrote a WebListener, and during the initialization I want to modify the wildfly configuration via management API. > I can read the configuration, but when I want to execute a delete or add request, nothing happens; the command does not return! There seems to be a deadlock. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3764) Problem with Infinispan and transactions

by Joel Sebastian (JIRA)

Joel Sebastian created WFLY-3764: ------------------------------------ Summary: Problem with Infinispan and transactions Key: WFLY-3764 URL: https://issues.jboss.org/browse/WFLY-3764 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Transactions, Web (Undertow) Affects Versions: 8.1.0.Final, 8.0.0.Final Environment: Operating System: Redhat 6 jdk1.7.0_51 x86_64 Reporter: Joel Sebastian Assignee: Tom Jenkinson We are using Jasing CAS 3.5.2 for Single Sign On purposes deployed on a server in a Wildfly 8.0.0 Final domain (yesterday we upgraded to 8.1.0 Final). The application is working just fine, but in sometimes we detect this error: 2014-08-22 00:30:50,365 ERROR [io.undertow.request] (default task-85) UT005023: Exception handling request to /SSO/login: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: Cookie name "comment" is a reserved token After this error the applications starts to fail with this error: 2014-08-22 00:31:24,387 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [15 seconds] on key [Urkr0TVHiwJ95KJnuhz9IB9n] for requestor [GlobalTransaction:<master:sso-server-1/web>:308:local]! Lock held by [GlobalTransaction:<master:sso-server-1/web>:296:local] 2014-08-22 00:31:24,407 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-91) ISPN000136: Execution error: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=308}, status=1} is not in a valid state to be invoking cache operations on. After this happens we need to restart the server, because the application cannot be restored from those errors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3580) Remoting LoginModule does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3580?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3580: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 953200|https://bugzilla.redhat.com/show_bug.cgi?id=953200] from MODIFIED to ASSIGNED > Remoting LoginModule does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3580 > URL: https://issues.jboss.org/browse/WFLY-3580 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, EJB > Reporter: Derek Horton > Assignee: Darran Lofthouse > > EJB/remoting configuration does not propagate the certificate as credentials for authentication if mutual auth SSL was used for the connection. This makes it impossible to get the certificate for use in a custom login module. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-764) Enhance the security realm plug-in mechanism for client-cert / external verification.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-764?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-764: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 953200|https://bugzilla.redhat.com/show_bug.cgi?id=953200] from MODIFIED to ASSIGNED > Enhance the security realm plug-in mechanism for client-cert / external verification. > ------------------------------------------------------------------------------------- > > Key: WFLY-764 > URL: https://issues.jboss.org/browse/WFLY-764 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Labels: Realm_Management > Fix For: Awaiting Volunteers > > > Currently verification is just based on the defined trust store - this is to take it one step further and allow an optional additional verification. > As a first step will need to ensure we have a suitable Callback from the authenticator to the realm to verify the identity and then this can be passed on to the plug-in. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3763) move as many as possible of the cli tests from wildfly to wildfly-core

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFLY-3763: --------------------------------------- Summary: move as many as possible of the cli tests from wildfly to wildfly-core Key: WFLY-3763 URL: https://issues.jboss.org/browse/WFLY-3763 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky The CLI testsuite really belongs next to the CLI sourcecode. Except those tests that require functionality not available in the core, e.g. data-source related commands, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-68) move as many as possible of the cli tests from wildfly to wildfly-core

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-68: --------------------------------------- Summary: move as many as possible of the cli tests from wildfly to wildfly-core Key: WFCORE-68 URL: https://issues.jboss.org/browse/WFCORE-68 Project: WildFly Core Issue Type: Task Security Level: Public (Everyone can see) Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky The CLI testsuite really belongs next to the CLI sourcecode. Except those tests that require functionality not available in the core, e.g. data-source related commands, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014