January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-900) Differently implemented password-stacking option in ClientLoginModule

by Martin Švehla (JIRA)

[ https://issues.jboss.org/browse/SECURITY-900?page=com.atlassian.jira.plug... ] Martin Švehla resolved SECURITY-900. ------------------------------------ Resolution: Won't Fix This issue is not backed by a valid use case and the difference in the login module behaviour is not a bug in this case. > Differently implemented password-stacking option in ClientLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-900 > URL: https://issues.jboss.org/browse/SECURITY-900 > Project: PicketBox > Issue Type: Bug > Affects Versions: PicketBox_4_9_2.Final > Reporter: Ondrej Lukas > > In case when some login module should use password stacking then value of password-stacking option should be set to useFirstPass. All login modules should respect it. However implemetation of org.jboss.security.ClientLoginModule uses password-stacking differently - it uses password stacking everytime when some value is set for password-stacking option (even value false). It should work same as other login modules. Current behavior can be confusing and can lead to incorrectly set server configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-409) Certificate Authority

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-409: ------------------------------------ Summary: Certificate Authority Key: ELY-409 URL: https://issues.jboss.org/browse/ELY-409 Project: WildFly Elytron Issue Type: Feature Request Components: Certificate Authority Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha1 This is a top level task to consider what we will need for certificate authority use within Elytron. I would imagine we would start with a fairly simple implementation ourselves within Elytron that can handle signing with the appropriate constraint checking / management of signed certificates, we would also want revocation, CRL generation, a simple OCSP responder. >From this we will have an API so that CA functions can be requested from within the application server, we will also have an SPI so that we can integrate with different CAs as an example FreeIPA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 edited comment on WFCORE-1330 at 1/28/16 6:58 AM: -------------------------------------------------------------------- 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 ? Could you also put all the logs on the restart, just to check if there is any clue why the contents are removed ? was (Author: ehugonnet): 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6084) Wrong code AdvancedADLdap for AdvancedADLdap login module

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-6084?page=com.atlassian.jira.plugin.... ] Hynek Švábek closed WFLY-6084. ------------------------------ > Wrong code AdvancedADLdap for AdvancedADLdap login module > --------------------------------------------------------- > > Key: WFLY-6084 > URL: https://issues.jboss.org/browse/WFLY-6084 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Hynek Švábek > Assignee: ANGELA ROBERTSON > > There is wrong short name for AdvancedADLdap login module. > In documentation is short name "AdvancedADLdap" with a uppercase letter "D". > In code is short name "AdvancedAdLdap" with a lowercase letter "d". > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > Change: > Short name: AdvancedADLdap > To: > Short name: AdvancedAdLdap -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5764) Remove mod_cluster excluded-context's default value with outdated contexts

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5764?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5764: --------------------------------- Workaround Description: Workaround for excluding no contexts is to set "excluded-contexts" to non-sense random value that will not match any real context. Workaround: Workaround Exists > Remove mod_cluster excluded-context's default value with outdated contexts > -------------------------------------------------------------------------- > > Key: WFLY-5764 > URL: https://issues.jboss.org/browse/WFLY-5764 > 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 > > > The list of current values is useless in the defualt configuration. > {code}"excluded-contexts" => "ROOT,invoker,jbossws,juddi,console"{code} > I am actually marking this as bug, because if you just want to use the root context, if you undefine the value, the default will be used which exludes root context. > Trying a "" value, results in a failure. > {code}[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value="" > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0113: '' is an invalid value for parameter excluded-contexts. Values must have a minimum length of 1 characters", > "rolled-back" => true, > "response-headers" => {"process-state" => "reload-required"} > }{code} > This all comes from legacy stuff. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6084) Wrong code AdvancedADLdap for AdvancedADLdap login module

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-6084?page=com.atlassian.jira.plugin.... ] Hynek Švábek resolved WFLY-6084. -------------------------------- Resolution: Won't Do I communicated with developers and they will do necessary changes in code. >From AdvancedAdLdap to value from documentation (AdvancedADLdap) > Wrong code AdvancedADLdap for AdvancedADLdap login module > --------------------------------------------------------- > > Key: WFLY-6084 > URL: https://issues.jboss.org/browse/WFLY-6084 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Hynek Švábek > Assignee: ANGELA ROBERTSON > > There is wrong short name for AdvancedADLdap login module. > In documentation is short name "AdvancedADLdap" with a uppercase letter "D". > In code is short name "AdvancedAdLdap" with a lowercase letter "d". > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > Change: > Short name: AdvancedADLdap > To: > Short name: AdvancedAdLdap -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 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)

10 years, 3 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)

10 years, 3 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)

10 years, 3 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)

10 years, 3 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 January 2016