October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-163) Monthly file rotation will continually overwrite the rotated log file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-163?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-163: ------------------------------------------------ Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1468746|https://bugzilla.redhat.com/show_bug.cgi?id=1468746] from ON_QA to VERIFIED > Monthly file rotation will continually overwrite the rotated log file > --------------------------------------------------------------------- > > Key: LOGMGR-163 > URL: https://issues.jboss.org/browse/LOGMGR-163 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 1.1.2.CR1, 1.2.3.GA, 1.3.3.Final, 1.4.4.Final, 1.5.8.Final, 2.0.7.Final, 2.1.0.Alpha2 > > > When the next rollover time is calculated a {{java.util.Calendar}} is used. When rotated monthly the day of the week is set to 0 and 1 month is added. This causes the calendar to be set to the last day of the current month. > On the last day of the month this also causes the file to continually rotate with each log message written, overwriting the previous log message. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9440) EJB and Undertow subsystems use org.wildfly.security.jacc-policy capability without registering a requirement for it

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-9440?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-9440: ------------------------------------ Assignee: Tomasz Adamski > EJB and Undertow subsystems use org.wildfly.security.jacc-policy capability without registering a requirement for it > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9440 > URL: https://issues.jboss.org/browse/WFLY-9440 > Project: WildFly > Issue Type: Bug > Components: EJB, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomasz Adamski > > Both EJB and Undertow have 'enable-jacc' attributes which, if true, result in the code doing a service dep using the org.wildfly.security.jacc-policy capability. But there's no registration of a requirement for that capability, so if it were removed (which requires reload) the inconsistent model would not be detected and a subsequent reboot/restart would fail. > This can't be fixed until WFCORE-3354 is, because right now that capability isn't registered either! > Fixing this isn't as simple as recording this as a fixed requirement of the relevant ejb/undertow capability, as it's only a requirement if the attribute value is 'true'. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1418) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1418?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved WFCORE-3349 to ELY-1418: ----------------------------------------- Project: WildFly Elytron (was: WildFly Core) Key: ELY-1418 (was: WFCORE-3349) Component/s: HTTP (was: Security) Affects Version/s: 1.2.0.Beta7 (was: 3.0.4.Final) > CLIENT_CERT without users certificates database > ----------------------------------------------- > > Key: ELY-1418 > URL: https://issues.jboss.org/browse/ELY-1418 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Affects Versions: 1.2.0.Beta7 > Reporter: Jan Kalina > Assignee: Jan Kalina > > CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. > Analysis document: > https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

by Robert Cernak (JIRA)

Robert Cernak created JGRP-2227: ----------------------------------- Summary: Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name Key: JGRP-2227 URL: https://issues.jboss.org/browse/JGRP-2227 Project: JGroups Issue Type: Bug Affects Versions: 4.0.6 Reporter: Robert Cernak Assignee: Bela Ban I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; In this way authentication should be false and I should get SecurityException. When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name. I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1170: --------------------------------------- You can't define the provider resolution on the trust managers, the provider discovery is defined on the SSLContext element or higher. The provider-name attribute is not inherited across different levels of configuration. > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1170: ----------------------------------- As I understand: 1. I can specify SSL-Context provider 2. I can specify TrustManager provider 3. If I don't specify SSLContext provider, then SSLContext will use root element provider 4. If I don't specify TrustManager provider, then TrustManager will use SSLContext provider My concern is point 4. And I am thinking if isn't better 4. If I don't specify TrustManager provider, then TrustManager will use root element provider > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the TrustManager within <authentication-client ></authentication>

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1385?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1385: ----------------------------------- It is still referenced in description "key and trust managers". That tricked me. I haven't realized we are talking about client ssl context, actually. In that case key manager is really not important here. > Add option to override the TrustManager within <authentication-client ></authentication> > ---------------------------------------------------------------------------------------- > > Key: ELY-1385 > URL: https://issues.jboss.org/browse/ELY-1385 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > > At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1276) Add methods on State to check current state

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-1276?page=com.atlassian.jira.plugin.s... ] Pedro Igor closed ELY-1276. --------------------------- > Add methods on State to check current state > ------------------------------------------- > > Key: ELY-1276 > URL: https://issues.jboss.org/browse/ELY-1276 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Affects Versions: 1.1.0.CR1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.CR5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1276) Add methods on State to check current state

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-1276?page=com.atlassian.jira.plugin.s... ] Pedro Igor updated ELY-1276: ---------------------------- Fix Version/s: 1.1.0.CR5 > Add methods on State to check current state > ------------------------------------------- > > Key: ELY-1276 > URL: https://issues.jboss.org/browse/ELY-1276 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Affects Versions: 1.1.0.CR1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.CR5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3363) CLI to output JSON

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3363: -------------------------------------------- Summary: CLI to output JSON Key: WFCORE-3363 URL: https://issues.jboss.org/browse/WFCORE-3363 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Add --output-json and associated XML element. It impacts: - Low level operation return value - echo-dmr displayed output - run-batch --verbose output Other commands are not impacted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 October 2017