November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5403: --------------------------------------- I'm fine with removing the extra level of configuration if JFC is, although you'll still have to support the old mod-cluster-config=configuration child resource for backwards compatibility. There is still the problem I mentioned above though re: the child resources under mod-cluster-config=configuration (DynamicLoadProviderDefinition, LoadMetricDefinition, CustomLoadMetricDefinition). If those resources are added after the initial add of the subsystem, and during boot, the result is the change isn't applied to the runtime and the server is put into reload-required. At a minimum we need to get it so if those are added after boot but as part of the same composite op that adds the subsystem, the reload isn't required. We can chat about how to do that. Ideally though some of those could be added at any time and the running service would be updated. Using a default of 'modcluster' for advertise is ok, but only if you track whether or not the value was actually set in the config. IOW, "undefined" in the model leads to trying to use "modcluster" and disabling advertise if unsuccessful. But any specifically defined value has to be correct or it's a failure. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Joe Wertz > Fix For: 7.2.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-5403: ------------------------------------- @[~brian.stansberry] No, I haven't seen it yet (since Joe didn't follow the Jira process and like the PR, nor does the commit itself reference this Jira...). I don't like this approach though (though for 7.1.x as workaround why not). By what I have done locally so far, as part of AS7-3623, removing the extra level of configuration and just leveraging GenericSubsystemDescribeHandler which enables you to add properties as parameters -- I like this very much. I am wondering now though, what is the best approach with requiring advertise. The goal is to provide users with best default configuration so we need to make sure that advertise is on by default. However, that means that users either need to specifi advertise-socket or disable advertise when adding the subsystem. How about: make the socket default to 'modcluster' abd if its defined just go with it, otherwise just disable advertise if its not.. PS: 4 comments above, the advertise-socket should be modcluster, not ajp. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Joe Wertz > Fix For: 7.2.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5833) Missing core queue attributes

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5833: -------------------------------- Summary: Missing core queue attributes Key: AS7-5833 URL: https://issues.jboss.org/browse/AS7-5833 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.3.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1 the messaging's subsystem queues does not expose all the HornetQ core queue attributes. Missing attributes: * dead-letter-address * expiry-address Incorrect attributes: * temporary is flagged as a read-only attribute but it must still be possible to set it when the queue is created => add it to the add operation parameters (default=false) -- 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

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] (AS7-6045) Add file handler back to logging.properties on initial boot

by James Perkins (JIRA)

James Perkins created AS7-6045: ---------------------------------- Summary: Add file handler back to logging.properties on initial boot Key: AS7-6045 URL: https://issues.jboss.org/browse/AS7-6045 Project: Application Server 7 Issue Type: Enhancement Components: Logging Reporter: James Perkins Assignee: James Perkins The file handler for the boot.log was removed when the logging subsystem changed to persist the logging.properties file. The default logging.properties should add the server.log configuration so the initial boot logging isn't lost. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3389) OSGi-fy drools-spring and drools-camel modules

by Alexander Filipchik (JIRA)

Alexander Filipchik created JBRULES-3389: -------------------------------------------- Summary: OSGi-fy drools-spring and drools-camel modules Key: JBRULES-3389 URL: https://issues.jboss.org/browse/JBRULES-3389 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-camel, drools-spring Affects Versions: 5.4.0.CR1 Reporter: Alexander Filipchik Assignee: Mark Proctor Fix For: 5.4.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
6
0 / 0

[JBoss JIRA] (AS7-6043) implement java version of JDR

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-6043: ---------------------------------- Summary: implement java version of JDR Key: AS7-6043 URL: https://issues.jboss.org/browse/AS7-6043 Project: Application Server 7 Issue Type: Feature Request Components: JDR Reporter: Jesse Jaggars Assignee: Jesse Jaggars Implement a pure java version of JDR to avoid the numerous issues encountered during productization. This should also resolve all the current issues for JDR. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3346) Security audit logging problem

by Jan Lanik (JIRA)

Jan Lanik created AS7-3346: ------------------------------ Summary: Security audit logging problem Key: AS7-3346 URL: https://issues.jboss.org/browse/AS7-3346 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.0.CR1b Reporter: Jan Lanik Assignee: Anil Saldhana I used the configuration setup + quick testing as documented here https://community.jboss.org/wiki/JBossAS7SecurityAuditing The audit.log file was created but no events was recorded in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

8
27
0 / 0

[JBoss JIRA] (AS7-4680) Logout a remote client from server and clearing login module cache.

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4680: ------------------------------------ Summary: Logout a remote client from server and clearing login module cache. Key: AS7-4680 URL: https://issues.jboss.org/browse/AS7-4680 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: java 1.6 win 7 64 bit 4 gb ram Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Blocker I have a custom login module. I authenticate and authorize a user (creating roles) by using this custom module. When i close the remote application, i want to logout the user from server so that clear login module cache, i.e deleting principals and roles from the cache. I couldn't find a solution for this problem in forum. If it exists, could you please explain it, thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
5
0 / 0

[JBoss JIRA] (AS7-4679) Catching custom login module exceptions in remote client

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4679: ------------------------------------ Summary: Catching custom login module exceptions in remote client Key: AS7-4679 URL: https://issues.jboss.org/browse/AS7-4679 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: Win 7 64 Bit 4 GB RAM java 1.6 Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Critical This feature request is related with the discussion: https://community.jboss.org/message/732948#732948 I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client, how is it possible??? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] (SECURITY-671) Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-671?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-671: -------------------------------------- Assignee: (was: Darran Lofthouse) > Negotiation/SPNEGO: Fallback to authenticate Form/Basic with ActiveDirectory > ---------------------------------------------------------------------------- > > Key: SECURITY-671 > URL: https://issues.jboss.org/browse/SECURITY-671 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: EAP 6.0.0 / JBossAS 7.1.2 > Reporter: Jochen Riedlinger > Attachments: krb5.conf, Krb5TicketInitiator.java, LBankSPNEGOLoginModule.java, part_of_standalone.xml > > > Since Version 4 of JBossAS we had our own implementations of a SPNEGOAuthenticator and SPNEGOLoginModule. While trying to migrate to EAP 6 I wanted to switch to your imlementation, because it is officially supported. > Unfortunately I find that your implementation is not yet finished because it lacks in a fallback solution that is able to validate username/password from BASIC/FORM authentication with ActiveDirectory. > Since I had this feature in my old implementation I want to offer to contribute it here to the Negotiation component of the project (unfortunately there is no JIRA component for Negotiation). > I think this would be valuable for anybody using SPNEGO. > My implementation would even word for remote-ejb-calls (with plain username password sent OR when sending a kerberos ticket in the password field) > If you are interested I'll upload my code and configuration instructions (RedHat employees can already see it in Support Case 00640390). -- 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

13 years, 5 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 November 2012