January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6085) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6085?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved SECURITY-935 to WFLY-6085: ------------------------------------------------- Project: WildFly (was: PicketBox ) Key: WFLY-6085 (was: SECURITY-935) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Security (was: Negotiation) > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: WFLY-6085 > URL: https://issues.jboss.org/browse/WFLY-6085 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6085) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6085?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-6085: ---------------------------------------- Sorry this one did need to be in WildFly - from first look I thought this was more implementation testing. > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: WFLY-6085 > URL: https://issues.jboss.org/browse/WFLY-6085 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1330) Deployment error after reboot [WFLYSRV0137]

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1330?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-1330: ------------------------------------------- It looks like the driver is in the MM-Controller-0.1.0-SNAPSHOT.war. Could you confirm that ? Is there a way for you to share your installation configuration as i can't seem to be able to reproduce your case ? > Deployment error after reboot [WFLYSRV0137] > ------------------------------------------- > > Key: WFCORE-1330 > URL: https://issues.jboss.org/browse/WFCORE-1330 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.2.Final > Environment: Ubuntu 14.04 LTS 64bit, jre-1.8.0_65 > Several deployed (JavaEE) web applications including non XA datasources that connect to a MySQL instance. > Reporter: Tobi Tobias > Assignee: ehsavoie Hugonnet > Priority: Critical > Attachments: server.log, server.log > > > I have a working configuration on wildfly 9.0.2 final with several web applications (JavaEE). > After a couple of days, I deployed another war file via jboss CLI. This application worked correctly and no deployment error occurred. > But if I restart the server now, I get following error message: > 10:36:01,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "MM-Controller-0.1.0-SNAPSHOT.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 966847a6f5f5bf8c3470f07ea9e65b7bbcdcd7b7 is available in the deployment content repository for deployment 'MM-Controller-0.1.0-SNAPSHOT.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart." > 10:36:01,990 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > I reproduced this at least 30 times - even with different jars. I always get this error. The server works fine as long as I don't reboot. > The only way to fix the configuration is to manually remove the deployments from the standalone.xml. > But this is not an option for me as I want to have the wildfly running as production server where I have several automatic deployments every day. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5756) Unable to exclude root context (/) via excluded-contexts in mod_cluster subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5756?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5756. -------------------------------- > Unable to exclude root context (/) via excluded-contexts in mod_cluster subsystem > --------------------------------------------------------------------------------- > > Key: WFLY-5756 > URL: https://issues.jboss.org/browse/WFLY-5756 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.CR5 > > > {noformat}[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value="ROOT,/"{noformat} > but no luck > {noformat} > mod_cluster/1.3.2.Alpha1-SNAPSHOT > Auto Refresh show DUMP output show INFO output > Node localhost (ajp://127.0.0.1:8009): > Enable Contexts Disable Contexts Stop Contexts > Balancer: syrah-cluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 77 > Virtual Host 1: > Contexts: > /clusterbench-passivating, Status: ENABLED Request: 0 Disable Stop > /, Status: ENABLED Request: 0 Disable Stop > Aliases: > localhost > default-host > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-5484: -------------------------------------- I think Undertow 1.3.16.Final should fix this, but I have not been able to get a reproducer to work. > Calling HttpServletRequest.logout() with single sign-on enabled only works every second time > -------------------------------------------------------------------------------------------- > > Key: WFLY-5484 > URL: https://issues.jboss.org/browse/WFLY-5484 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Richard Janík > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 10.0.0.CR5 > > Attachments: reproducer-jbeap-1282.zip > > > See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect > This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-935) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-935?page=com.atlassian.jira.plug... ] Darran Lofthouse reopened SECURITY-935: --------------------------------------- > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: SECURITY-935 > URL: https://issues.jboss.org/browse/SECURITY-935 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-935) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-935?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on SECURITY-935: ------------------------------------------- Will fix. > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: SECURITY-935 > URL: https://issues.jboss.org/browse/SECURITY-935 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1334) Allow disabling audit log rotation

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1334?page=com.atlassian.jira.plugi... ] Tomas Hofman commented on WFCORE-1334: -------------------------------------- [~brian.stansberry] only now I noticed that audit log is deprecated in Wildfly. There is no ticket mentioned in the commit, does it have some replacement? Does it make sense to make improvements on it if it's going to be removed? > Allow disabling audit log rotation > ---------------------------------- > > Key: WFCORE-1334 > URL: https://issues.jboss.org/browse/WFCORE-1334 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 2.0.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1301554 > org.jboss.as.controller.audit.FileAuditLogHandler always rotates audit-log.log at startup/reload. An option to disable log rotation is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6077) Add auto-create|delete-jms-queues to address-settings resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6077?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reopened WFLY-6077: ------------------------------- > Add auto-create|delete-jms-queues to address-settings resource > -------------------------------------------------------------- > > Key: WFLY-6077 > URL: https://issues.jboss.org/browse/WFLY-6077 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.CR5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6048) jboss-webservices.xml descriptor doesn't override @WebContext annotation

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6048?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-6048: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Alessio Soldano) > jboss-webservices.xml descriptor doesn't override @WebContext annotation > ------------------------------------------------------------------------ > > Key: WFLY-6048 > URL: https://issues.jboss.org/browse/WFLY-6048 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.2.Final > Environment: ubuntu 14.04, Java 7 > Reporter: Wojciech Oczkowski > Assignee: Dmitrii Tikhomirov > Priority: Minor > Attachments: ws-xml-override.zip > > > It seems that annotation WebConfig takes precedence over jboss-webservices.xml descriptor values. It doesn't seem right as you cannot override annotation values for test purposes for example. > Problematic code seems to be: > org.jboss.as.webservices.metadata.AbstractMetaDataBuilderEJB:159 > (should prefer JBossPortComponentMetaData over EJBEndpoint) > and > org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect:177 > (should prefer EJBSecurityMetaData over annotation value) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

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 January 2016