March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-809) Release JBoss Negotiation 2.3.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-809: ----------------------------------------- Summary: Release JBoss Negotiation 2.3.0.Beta1 Key: SECURITY-809 URL: https://issues.jboss.org/browse/SECURITY-809 Project: PicketBox Issue Type: Release Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_3_0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-807) Add a LoginModule to wrap existing Kerberos LoginModule(s) and optionally add a GSSCredential

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-807?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-807. --------------------------------------- Fix Version/s: Negotiation_2_3_0.Beta1 (was: Negotiation_2_3_0_CR1) Resolution: Done > Add a LoginModule to wrap existing Kerberos LoginModule(s) and optionally add a GSSCredential > --------------------------------------------------------------------------------------------- > > Key: SECURITY-807 > URL: https://issues.jboss.org/browse/SECURITY-807 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: Negotiation_2_3_0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3143) Upgrade to JBoss Negotiation 2.3.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3143: -------------------------------------- Summary: Upgrade to JBoss Negotiation 2.3.0.Beta1 Key: WFLY-3143 URL: https://issues.jboss.org/browse/WFLY-3143 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 9.0.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2229) Add support for PKCS12 Keystores in security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2229?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2229: ----------------------------------- Priority: Critical (was: Major) > Add support for PKCS12 Keystores in security realms. > ---------------------------------------------------- > > Key: WFLY-2229 > URL: https://issues.jboss.org/browse/WFLY-2229 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security, > Fix For: 9.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2229) Add support for PKCS12 Keystores in security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2229?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2229: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) > Add support for PKCS12 Keystores in security realms. > ---------------------------------------------------- > > Key: WFLY-2229 > URL: https://issues.jboss.org/browse/WFLY-2229 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security, > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2890) Add support for PKCS#11 configuration within security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2890?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2890: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) > Add support for PKCS#11 configuration within security realms. > ------------------------------------------------------------- > > Key: WFLY-2890 > URL: https://issues.jboss.org/browse/WFLY-2890 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: eap, management_security, > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2903) Create Version 2.1 of the domain management schema

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2903?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2903: ----------------------------------- Priority: Blocker (was: Critical) > Create Version 2.1 of the domain management schema > -------------------------------------------------- > > Key: WFLY-2903 > URL: https://issues.jboss.org/browse/WFLY-2903 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.1.Final > > > Before additional configuration changes can be made a new version of the domain management schema is required - it is better to do this in it's own commit instead of a race for the first issue to add it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3108) Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3108?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3108: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1076066|https://bugzilla.redhat.com/show_bug.cgi?id=1076066] from MODIFIED to ON_QA > Can't promote --backup slave HC to master and reload without moving domain.cached-remote.xml > -------------------------------------------------------------------------------------------- > > Key: WFLY-3108 > URL: https://issues.jboss.org/browse/WFLY-3108 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.1.Final > > > The prescribed mechanism for converting a slave HC to master is to: > 1) Start the slave with --backup so a local copy of the domain config is maintained (in file domain.cached-remote.xml). > 2) Stop the existing master. > 3) Use the cli to connect to the slave and > /host=<slavename>:write-local-domain-controller > 4) Then, in the CLI > reload --host=<slavename> > Problem is this fails because the HC expects to have a domain config file "domain.xml". > 2014-03-13 09:54:04,829 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:514) [wildfly-host-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/WF801/slave/domain/configuration/domain.xml (No such file or directory) > at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45] > at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:100) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT] > ... 3 more > Or, MUCH WORSE, there happens to be a random domain.xml in the filesystem, which has content that is out of sync with the correct domain config. This domain.xml config will be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3005) cannot override logging.configuration in jboss-cli.sh and jboss-cli.bat

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3005?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky resolved WFLY-3005. ------------------------------------- Fix Version/s: 8.0.1.Final Resolution: Done Merged. > cannot override logging.configuration in jboss-cli.sh and jboss-cli.bat > ----------------------------------------------------------------------- > > Key: WFLY-3005 > URL: https://issues.jboss.org/browse/WFLY-3005 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Final > Environment: windows and linux > Reporter: Gabriele Garuglieri > Assignee: Alexey Loubyansky > Fix For: 8.0.1.Final > > > when using cli scripts jboss-cli.sh and jboss-cli.bat and you cannot write in $JBOSS_HOME because it is serving many server instances, you can override default jboss-cli.xml setting -Djboss.cli.config in $JAVA_OPTS but you cannot override logging.configuration because in both scripts is set with default after expanding $JAVA_OPTS > last lines of bat script could be modified as follows: > echo "%JAVA_OPTS%" | findstr /I "logging.configuration" > nul > if errorlevel == 1 ( > set "JAVA_OPTS=%JAVA_OPTS% -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties" > ) else ( > echo logging.configuration already set in JAVA_OPTS > ) > "%JAVA%" %JAVA_OPTS% ^ > -jar "%JBOSS_RUNJAR%" ^ > -mp "%JBOSS_MODULEPATH%" ^ > org.jboss.as.cli ^ > %* > Last lines of sh script could be modified as follows: > LOG_CONF=`echo $JAVA_OPTS | $GREP "logging.configuration"` > if [ "x$LOG_CONF" = "x" ]; then > JAVA_OPTS="$JAVA_OPTS -Dlogging.configuration=file:$JBOSS_HOME/bin/jboss-cli-logging.properties" > else > echo "logging.configuration already set in JAVA_OPTS" > fi > # Sample JPDA settings for remote socket debugging > #JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n" > eval \"$JAVA\" $JAVA_OPTS -jar \"$JBOSS_HOME/jboss-modules.jar\" -mp \"${JBOSS_MODULEPATH}\" org.jboss.as.cli '"$@"' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3101) CLI: hide stacktraces for exceptions w/o messages when logging errors

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3101?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky resolved WFLY-3101. ------------------------------------- Resolution: Done Merged. > CLI: hide stacktraces for exceptions w/o messages when logging errors > --------------------------------------------------------------------- > > Key: WFLY-3101 > URL: https://issues.jboss.org/browse/WFLY-3101 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Final > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 8.0.1.Final > > > CommandContextImpl contains the following logic > public void handleSafe(String line) { > exitCode = 0; > try { > handle(line); > } catch(Throwable t) { > final StringBuilder buf = new StringBuilder(); > buf.append(t.getLocalizedMessage()); > Throwable t1 = t.getCause(); > while(t1 != null) { > if(t1.getLocalizedMessage() != null) { > buf.append(": ").append(t1.getLocalizedMessage()); > } else { > t1.printStackTrace(); > } > t1 = t1.getCause(); > } > error(buf.toString()); > } > } > When an exception does not contain any message, e.g. in some cases IllegalArgumentException, etc, the full stacktraces are logged that are useful for debugging but not nice from the user interface point of view. It was suggested to hide them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 March 2014