February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-13991) Artemis should not delete corrupted log files

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13991?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13991: ---------------------------------- Summary: Artemis should not delete corrupted log files (was: Artemis should not delete corrupt log files) > Artemis should not delete corrupted log files > --------------------------------------------- > > Key: WFLY-13991 > URL: https://issues.redhat.com/browse/WFLY-13991 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 21.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > When a corrupted artemis journal file is seen Artemis shuts down EAP, but before it does that it deletes the corrupted file. This means that no after the event analysis/investigation can be done as the corrupted journal file is gone. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-6660) Allow dumping Artemis journal to file using WildFly Management API

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-6660?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-6660: --------------------------------- Summary: Allow dumping Artemis journal to file using WildFly Management API (was: Allow to dump Artemis journal to file using WildfFly Management API) > Allow dumping Artemis journal to file using WildFly Management API > ------------------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.redhat.com/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Emmanuel Hugonnet > Priority: Major > Attachments: journal.txt > > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5291) Upgrade Elytron Web to 1.9.0.CR1

by Farah Juma (Jira)

Farah Juma created WFCORE-5291: ---------------------------------- Summary: Upgrade Elytron Web to 1.9.0.CR1 Key: WFCORE-5291 URL: https://issues.redhat.com/browse/WFCORE-5291 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 15.0.0.Beta1 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5290) Upgrade WildFly Elytron to 1.15.0.CR1

by Farah Juma (Jira)

Farah Juma created WFCORE-5290: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.15.0.CR1 Key: WFCORE-5290 URL: https://issues.redhat.com/browse/WFCORE-5290 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 15.0.0.Beta1 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-128) Release Elytron Web 1.9.0.CR1

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-128?page=com.atlassian.jira.plugi... ] Farah Juma resolved ELYWEB-128. ------------------------------- Resolution: Done > Release Elytron Web 1.9.0.CR1 > ----------------------------- > > Key: ELYWEB-128 > URL: https://issues.redhat.com/browse/ELYWEB-128 > Project: Elytron Web > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-243) Ensure reference to repository is removed from pom

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-243?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-243: --------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Ensure reference to repository is removed from pom > -------------------------------------------------- > > Key: ELY-243 > URL: https://issues.redhat.com/browse/ELY-243 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.15.0.CR2 > > > We need to ensure the reference to the JBoss repo is removed from the pom and artefacts are available from Maven Central. > Also at this point probably good to put the steps in place for Elytron to also be available from Maven Central. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-533) Deprecate all legacy code

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-533?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-533: --------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.redhat.com/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.15.0.CR2 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1440) FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1440?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1440: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1440 > URL: https://issues.redhat.com/browse/ELY-1440 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.15.0.CR2 > > > This API was introduced to cover the case where authentication happens late in a request, generally that is quite a rare event. > Even though the API may be popular it would likely happen once for a session and all future requests for that session the identity would be known in advance. > At the moment by not running as the existing identity we are loosing all automatic identity outflow opportunities as calls pass from the servlet container to the EJB container. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1682) Fallback to another SASL client mechanism when SASL client initialisation fails

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1682?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1682: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Fallback to another SASL client mechanism when SASL client initialisation fails > ------------------------------------------------------------------------------- > > Key: ELY-1682 > URL: https://issues.redhat.com/browse/ELY-1682 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.7.0.CR1 > Reporter: Martin Choma > Priority: Major > Fix For: 1.15.0.CR2 > > Attachments: org.jboss.eapqe.krbldap.eap71.tests.krb.ejb.KerberosEjbGssapiTestCase-output.txt > > > {code:title=HipChat conversation} > Martin Choma: I have got this situation here; Server is authenticated with GSSAPI and PLAIN. Client has only username/password credential - no kerberos credential. > But client tries to create GssapiSaslClient as well (which make problem on IBM). Once I set .setSaslMechanismSelector(SaslMechanismSelector.fromString("PLAIN")) scenario works ok. > I wonder could Authentication Client be smart enough to not try to initialize authentication mechanisms which it has not credentials for? > Darran Lofthouse: Client side GSSAPI we tend not to have configured credentials as the mech obtains from OS level. The mech should fail and allow the next mech to be selected > Martin Choma: Ok, so I will create issue. Seems on client side this mechanism fallback does not work properly. (At least in IBM JDK case). > In this case it is initialization of mechanism which is failing, so maybe fallback does not have chance to get involved. > Darran Lofthouse: Sounds possible, if a mech can not initialise we should likely treat it as a failed mech and move on - maybe something needed in Remoting > though for that one as that is where that loop happens but start with an ELY issue > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-1724) Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource'

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1724?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1724: ---------------------------- Fix Version/s: 1.15.0.CR2 (was: 1.15.0.CR1) > Develop an alternative to 'org.wildfly.security.credential.source.OAuth2CredentialSource' > ----------------------------------------------------------------------------------------- > > Key: ELY-1724 > URL: https://issues.redhat.com/browse/ELY-1724 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.15.0.CR2 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 February 2021