November 2012 - jboss-jira - Jboss List Archives

[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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4823) add-user has the ability to add a user and edit/replace a user - we should add delete a user

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4823: ------------------------------------- Summary: add-user has the ability to add a user and edit/replace a user - we should add delete a user Key: AS7-4823 URL: https://issues.jboss.org/browse/AS7-4823 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 For completeness the add-user utility should also support an option for deleting / disabling users. If we go for disabling rather than deleting we may then also want enabling - the re-writes of the properties files retain the comments so a disable / enable mechanism would be easiest to just comment out the disabled user. -- 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

12 years, 11 months

1
2
0 / 0

[JBoss JIRA] (AS7-4049) Revisit the JBOSS_LOCAL_USER Mechanism

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4049: ------------------------------------- Summary: Revisit the JBOSS_LOCAL_USER Mechanism Key: AS7-4049 URL: https://issues.jboss.org/browse/AS7-4049 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse There are various points to reconsider: - - Implementation becoming quite embedded in the RealmSecurityProviderService - No local configuration within the realms - No http equivalent -- 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

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-2564) Allow genuine cross-origin resource sharing requests for domain management

by Darran Lofthouse (Created) (JIRA)

Allow genuine cross-origin resource sharing requests for domain management -------------------------------------------------------------------------- Key: AS7-2564 URL: https://issues.jboss.org/browse/AS7-2564 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Minor Fix For: 7.2.0.Alpha1 There may be future scenarios where cross-origin requests could be supported such as custom web/admin applications deployed to different to a different server. This issue is to implement both configuration for accepted requests and support for the OPTIONS method. -- 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

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] (JGRP-1542) RELAY2: preserve messages flags when forwarding / routing / delivering messages

by Bela Ban (JIRA)

Bela Ban created JGRP-1542: ------------------------------ Summary: RELAY2: preserve messages flags when forwarding / routing / delivering messages Key: JGRP-1542 URL: https://issues.jboss.org/browse/JGRP-1542 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.3 When forwarding a message to the local site master, routing a message from the site master over the bridge to a remote site master and delivering a message received from a remote site master in the local site, the original message M is marshalled into a byte buffer and tucked into a new message M'. However, M' does *not* copy the flags of M. So, for instance, if M was tagged as OOB, M' won't be OOB, therefore forwarding, routing and delivering locally won't be done on the OOB thread pool. Only when M' is unpacked, then M will have the original flags preserved. SOLUTION: Copy the flags of the original message into the wrapping message used to forward, route and deliver the original message. -- 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, 11 months

1
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012