June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-535) add config to force use of remote invoker instead of local

by Tom Elrod (JIRA)

add config to force use of remote invoker instead of local ---------------------------------------------------------- Key: JBREM-535 URL: http://jira.jboss.com/jira/browse/JBREM-535 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) With the change to having InvokerLocator.BYVALUE config use local invoker and cloning of value instead of using remote invoker (see JBREM-320), now need a specific config for forcing use of remote invoker instead of local even when in same jvm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-536) turn off host verification when doing push callback from server using same ssl config as server

by Tom Elrod (JIRA)

turn off host verification when doing push callback from server using same ssl config as server ----------------------------------------------------------------------------------------------- Key: JBREM-536 URL: http://jira.jboss.com/jira/browse/JBREM-536 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: security Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Since will not have the ServerinvokerCallbackHandler pick up ssl config from the server when creating push callback client back to callback server, will need to turn off host verification as well as setting the client mode (which is already being done). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-993) make assignment handlers configurable

by Martin Goldhahn (JIRA)

make assignment handlers configurable ------------------------------------- Key: JBPM-993 URL: http://jira.jboss.com/jira/browse/JBPM-993 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: N/A Reporter: Martin Goldhahn Assigned To: Tom Baeyens The JpdlXmlReader contains a hard-coded reference to both org.jbpm.identity.assignment.ExpressionAssignmentHandler and org.jbpm.taskmgmt.assignment.ActorAssignmentHandler. We need this parameter to be configurable, e.g. being able to use our own ExpressionAssignmentHandler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (SECURITY-35) JSR-196 Provider Implementation

by Anil Saldhana (JIRA)

JSR-196 Provider Implementation ------------------------------- Key: SECURITY-35 URL: http://jira.jboss.com/jira/browse/SECURITY-35 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.1 Clean up the JSR-196 configuration as well as the auth module implementations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-16) Inject options on AuthorizationManagerService

by Anil Saldhana (JIRA)

Inject options on AuthorizationManagerService --------------------------------------------- Key: SECURITY-16 URL: http://jira.jboss.com/jira/browse/SECURITY-16 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 AuthorizationManagerService can have an injection of options that can then be passed on to the various pluggable Authorization Managers. Each of the Authorization Managers can have an optional setOptions method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4087) SFSB.getCallerPrincipal() from before- and afterCompletion

by Alexey Loubyansky (JIRA)

SFSB.getCallerPrincipal() from before- and afterCompletion ---------------------------------------------------------- Key: JBAS-4087 URL: http://jira.jboss.com/jira/browse/JBAS-4087 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Alexey Loubyansky Assigned To: Anil Saldhana One should be able to call ctx.getCallerPrincipal() from SFSB's afterBegin, before- and afterCompletion. See "7.6.1 Operations Allowed in the Methods of a Stateful Session Bean Class" of the EJB2.1 spec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3445) Testcase for UTF-8 support with FORM Authentication

by Anil Saldhana (JIRA)

Testcase for UTF-8 support with FORM Authentication --------------------------------------------------- Key: JBAS-3445 URL: http://jira.jboss.com/jira/browse/JBAS-3445 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.6.CR1 User says: ======================================================== I have run into as well using JBoss 4.0.3SP1 (and 4.0.4GA). In my Web Applications, I can login with English usernames and passwords just fine. But when I try to login with a Russian or Chineese username, the login always fails. >From the tracing I've done, it seems the username is getting converted to ISO-8859-1, and that's why it's failing. I've done all the "standard" things to make our pages UTF-8, and this does work on every page except the login page. Something about "j_security_check" is ignoring UTF-8 and forcing a conversion to "ISO-8859-1". ========================================================= -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (SECURITY-41) JaasSecurityManagerService can show security provider/JCA algorithm information

by Anil Saldhana (JIRA)

JaasSecurityManagerService can show security provider/JCA algorithm information ------------------------------------------------------------------------------- Key: SECURITY-41 URL: http://jira.jboss.com/jira/browse/SECURITY-41 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Priority: Minor Fix For: 2.0.GA JBAS-3400 has the information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-3400) JaasSecurityManagerService can show security provider/JCA algorithm information

by Anil Saldhana (JIRA)

JaasSecurityManagerService can show security provider/JCA algorithm information ------------------------------------------------------------------------------- Key: JBAS-3400 URL: http://jira.jboss.com/jira/browse/JBAS-3400 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Sohil Shah Priority: Optional Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP2 It may be useful to determine the security providers and the various JCA algorithms installed in the JDK. So, add two methods to the JaasSecurityManagerService as follows: - showProviders() - getAlgorithm(String serviceName) If the serviceName is null, show all the possible JCA service names. Here is a partial tested code, that you may want to adapt: ====================================================================================== import java.security.*; import java.util.*; public class A { public static void main(String[] args) { Provider[] providers = Security.getProviders(); for(int i = 0; i < providers.length; i++) { System.out.println("Provider="+providers[i].toString()); } System.out.println("Printing JCA Algorithm Information"); printJCAAlgorithm("Cipher"); printJCAAlgorithm("Signature"); printJCAAlgorithm("KeyFactory"); printJCAAlgorithm("SecretKeyFactory"); printJCAAlgorithm("AlgorithmParameters"); printJCAAlgorithm("MessageDigest"); printJCAAlgorithm("Mac"); } private static void printJCAAlgorithm(String sName) { System.out.println("Printing "+sName); Set md2 = Security.getAlgorithms(sName); System.out.println(sName + " set length="+md2.size()); Iterator md2iter = md2.iterator(); while(md2iter.hasNext()) { System.out.println(md2iter.next().toString()); } } } ==================================================================================== The output is: asaldhana~/testSecurity>java -cp . -Djava.security.manager A Provider=SUN version 1.5 Provider=SunRsaSign version 1.5 Provider=SunJSSE version 1.5 Provider=SunJCE version 1.5 Provider=SunJGSS version 1.0 Provider=SunSASL version 1.5 Printing JCA Algorithm Information Printing Cipher Cipher set length=13 ARCFOUR PBEWITHSHA1ANDDESEDE DESEDEWRAP PBEWITHMD5ANDTRIPLEDES DESEDE RSA AESWRAP AES PBEWITHMD5ANDDES BLOWFISH DES RC2 PBEWITHSHA1ANDRC2_40 Printing Signature Signature set length=9 SHA256WITHRSA NONEWITHDSA .... Make the changes in HEAD. I will port it to Branch_4_0 and Branch_3_2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

5
13
0 / 0

[JBoss JIRA] Created: (SECURITY-37) Programmatic Web Authentication

by Anil Saldhana (JIRA)

Programmatic Web Authentication ------------------------------- Key: SECURITY-37 URL: http://jira.jboss.com/jira/browse/SECURITY-37 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.GA This does not come directly under JBossSX. But more from JBAS integration perspective. This is just a tracking issue for JBAS-4077 in JBoss 5.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
3
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 June 2007