June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8911) Elytron: Update test to be agnostic of modifiable realm identity iteration

by David Lloyd (JIRA)

David Lloyd created WFLY-8911: --------------------------------- Summary: Elytron: Update test to be agnostic of modifiable realm identity iteration Key: WFLY-8911 URL: https://issues.jboss.org/browse/WFLY-8911 Project: WildFly Issue Type: Task Components: Security Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2939) Disabled deployments in server group enabled after WAR is updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2939: ---------------------------------------- Assignee: (was: Jason Greene) > Disabled deployments in server group enabled after WAR is updated > ----------------------------------------------------------------- > > Key: WFCORE-2939 > URL: https://issues.jboss.org/browse/WFCORE-2939 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Environment: Centos 7 > OpenJDK > Reporter: Matthew Casperson > > Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1234) AuthenticationConfiguration.useDefaultProviders is no longer using our default.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1234?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1234: ---------------------------------- Fix Version/s: 1.1.0.Beta52 (was: 1.1.0.Beta53) > AuthenticationConfiguration.useDefaultProviders is no longer using our default. > ------------------------------------------------------------------------------- > > Key: ELY-1234 > URL: https://issues.jboss.org/browse/ELY-1234 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta52 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1232) Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1232?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1232: ---------------------------------- Fix Version/s: 1.1.0.Beta52 (was: 1.1.0.Beta53) > Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing > --------------------------------------------------------------------------------------------------------- > > Key: ELY-1232 > URL: https://issues.jboss.org/browse/ELY-1232 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: David Lloyd > Priority: Blocker > Labels: eap7.1-rfe-failure, eap7.1-tests-blocked > Fix For: 1.1.0.Beta52 > > > I'm not able to get SCRAM PLUS SASL mechanisms (i.e. the ones with channel binding) working. It seems there is a missing piece of integration. The mechanisms are required by EAP7-530. > I don't see the wrapper SASL factories, which are responsible for handling {{ChannelBindingCallback}}, used in the application server. (e.g. the {{TLSServerEndPointChannelBindingSaslClientFactory}}). > This issue is blocking test development. > There is still a chance the problem is in my test configuration, but the documentation of this topic is still a little bit sparse. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2939) Disabled deployments in server group enabled after WAR is updated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8909 to WFCORE-2939: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2939 (was: WFLY-8909) Component/s: Domain Management (was: Server) Affects Version/s: (was: 11.0.0.Alpha1) > Disabled deployments in server group enabled after WAR is updated > ----------------------------------------------------------------- > > Key: WFCORE-2939 > URL: https://issues.jboss.org/browse/WFCORE-2939 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Environment: Centos 7 > OpenJDK > Reporter: Matthew Casperson > Assignee: Jason Greene > > Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2938) Ensure an SSLContext from an injected legacy security realm is used for a remote outbound connection regardless of whether or not a username is specified

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2938?page=com.atlassian.jira.plugi... ] Farah Juma moved JBEAP-11435 to WFCORE-2938: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2938 (was: JBEAP-11435) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR19) > Ensure an SSLContext from an injected legacy security realm is used for a remote outbound connection regardless of whether or not a username is specified > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2938 > URL: https://issues.jboss.org/browse/WFCORE-2938 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1475) Convert project to use i18n logging and exceptions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1475?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1475: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1330729|https://bugzilla.redhat.com/show_bug.cgi?id=1330729] from ON_QA to VERIFIED > Convert project to use i18n logging and exceptions > -------------------------------------------------- > > Key: JGRP-1475 > URL: https://issues.jboss.org/browse/JGRP-1475 > Project: JGroups > Issue Type: Task > Reporter: James Perkins > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2 > > > As per [ANDIAMO-7|https://issues.jboss.org/browse/ANDIAMO-7] all messages (logged and exceptions) need a unique id. This need to be done using JBoss Logging, [ANDIAMO-2|https://issues.jboss.org/browse/ANDIAMO-2]. See [https://community.jboss.org/docs/DOC-18453] for information on configuring the loggers and message bundles. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1236) Release WildFly Elytron 1.1.0.Beta52

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1236: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.Beta52 Key: ELY-1236 URL: https://issues.jboss.org/browse/ELY-1236 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta52 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2937) Upgrade to WildFly Elytron 1.1.0.Beta52

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2937?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-11434 to WFCORE-2937: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2937 (was: JBEAP-11434) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade to WildFly Elytron 1.1.0.Beta52 > --------------------------------------- > > Key: WFCORE-2937 > URL: https://issues.jboss.org/browse/WFCORE-2937 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1958) RequestCorrelator "channel is not connected" error during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1958?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1958: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1399195|https://bugzilla.redhat.com/show_bug.cgi?id=1399195] from ON_QA to VERIFIED > RequestCorrelator "channel is not connected" error during shutdown > ------------------------------------------------------------------ > > Key: JGRP-1958 > URL: https://issues.jboss.org/browse/JGRP-1958 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.12 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.5 > > > Error logged during shutdown of a channel due to RequestCorrelator failing to send a reply: > ERROR [org.jgroups.protocols.UNICAST2] (OOB-17,shared=tcp) couldn't deliver OOB message [dst: server1/web, src: server2/web (4 headers), size=62 bytes, flags=OOB|DONT_BUNDLE|RSVP]: java.lang.IllegalStateException: channel is not connected > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:617) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:544) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > [incoming JGroups message] > It appears to just be a timing issue between shutdown of the channel and RequestCorrelator processing the message, which triggers a response message. > It would be good to either avoid triggering the exception in the first place, or suppress the error log during shutdown. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017