April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3877) Use SeamGlobalResolver in the RuleBasedPermissionResolver as it is in ManagedWorkingMemory

by Jarek Gilewski (JIRA)

Use SeamGlobalResolver in the RuleBasedPermissionResolver as it is in ManagedWorkingMemory ------------------------------------------------------------------------------------------ Key: JBSEAM-3877 URL: https://jira.jboss.org/jira/browse/JBSEAM-3877 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA Reporter: Jarek Gilewski SeamGlobalResolver is not used by RuleBasedPermissionResolver, so the global variable is not resolved. (Details on the forum) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3882) PermissionResolvers can't use injections

by Clint Popetz (JIRA)

PermissionResolvers can't use injections ---------------------------------------- Key: JBSEAM-3882 URL: https://jira.jboss.org/jira/browse/JBSEAM-3882 Project: Seam Issue Type: Bug Components: Security Reporter: Clint Popetz PermissionResolvers are seam components, and the documentation doesn't mention any restrictions on them. However, because PermissionMapper caches the resolver chain in the application, and doesn't serialize access to the resolvers themselves, PermissionResolvers must not only be stateless but also must not use injections, even of stateless components, as bijection on each resolver might be interlaced from multiple threads. This should probably be documented, as it just exposed itself as on our production server as nasty errors under load :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3437) Create protected isInitialized() and setInitialized( boolean ) methods in Credentials

by Mike Pettypiece (JIRA)

Create protected isInitialized() and setInitialized( boolean ) methods in Credentials ------------------------------------------------------------------------------------- Key: JBSEAM-3437 URL: https://jira.jboss.org/jira/browse/JBSEAM-3437 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Mike Pettypiece It would be useful if there were protected methods isInitialized() and setInitialized( boolean ) in Credentials. I'm currently subclassing Credentials and right now I need access to the field "initialized". Having to shadow initialized (along with username and overriding it's get/setters) isn't ideal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2890) NTLM integration

by Pete Muir (JIRA)

NTLM integration ---------------- Key: JBSEAM-2890 URL: http://jira.jboss.com/jira/browse/JBSEAM-2890 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.A1, 2.0.2.CR1 Reporter: Pete Muir Provide deeper integration with NTLM (and similar systems?) - for example a simple component which exposes the user logged in via NTLM, and automatically pushes that info into identity? -- 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

16 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4109) Typo "Vehciel" in PersistenceProvider comments

by Julien Kronegg (JIRA)

Typo "Vehciel" in PersistenceProvider comments ---------------------------------------------- Key: JBSEAM-4109 URL: https://jira.jboss.org/jira/browse/JBSEAM-4109 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.CR1 Environment: http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/persis... Reporter: Julien Kronegg Priority: Trivial A comment contains a query "select count(v) from Vehciel v" where the class name has a typo: it should be "Vehicle" not "Vehciel" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3814) org.jboss.seam.log.LogProvider should offer variable parameter list like org.jboss.seam.log.Log to improve logging performace

by Francisco Jose Peredo Noguez (JIRA)

org.jboss.seam.log.LogProvider should offer variable parameter list like org.jboss.seam.log.Log to improve logging performace ----------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3814 URL: https://jira.jboss.org/jira/browse/JBSEAM-3814 Project: Seam Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez This could be accomplished easily if Slf4j is used as the underlying tech for logging since it is already supported. The change could be done without any code modifications and then the logging calls could be optimized gradually. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4111) wicket example - Can't instantiate page using constructor

by Jozef Hartinger (JIRA)

wicket example - Can't instantiate page using constructor --------------------------------------------------------- Key: JBSEAM-4111 URL: https://jira.jboss.org/jira/browse/JBSEAM-4111 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.2.CR1 Environment: JBoss AS 4.2.3.GA, JBoss AS 5.0.1.GA JDK 5 update 16 Reporter: Jozef Hartinger Priority: Critical Fix For: 2.1.2.GA Application fails when selecting a hotel from the search page. See attached log for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4112) wicket example - runtime instrumentation broken

by Jozef Hartinger (JIRA)

wicket example - runtime instrumentation broken ----------------------------------------------- Key: JBSEAM-4112 URL: https://jira.jboss.org/jira/browse/JBSEAM-4112 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.2.CR1 Environment: JBoss AS 5.0.1.GA JDK 5 update 16 runtime instrumentation Reporter: Jozef Hartinger Priority: Critical Fix For: 2.1.2.GA Attachments: wicket-runtime.txt Example deploys, but opening home page fails with exception -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3761) Support EL for 'hash' attribute of @UserPassword

by Ingo Jobling (JIRA)

Support EL for 'hash' attribute of @UserPassword ------------------------------------------------- Key: JBSEAM-3761 URL: https://jira.jboss.org/jira/browse/JBSEAM-3761 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.SP1 Reporter: Ingo Jobling Would it be possible to support EL so we could do something like: @UserPassword(hash = "#{applicationProperties.get('security.password.digestAlgorithm')}") Feature request opened per reply by Shane Bryzak to Seam Forum post : http://www.seamframework.org/Community/SaltForUserPasswordInSeam21#commen... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3762) Make it possible to select password salt without overriding IdentityStore

by Nikolay Elenkov (JIRA)

Make it possible to select password salt without overriding IdentityStore ------------------------------------------------------------------------- Key: JBSEAM-3762 URL: https://jira.jboss.org/jira/browse/JBSEAM-3762 Project: Seam Issue Type: Feature Request Components: Security Environment: Seam 2.1 Reporter: Nikolay Elenkov Currently, JpaIdentityStore uses the username as salt when hashing the user password. If you want to use a different property as salt, you need to override JpaIdentityStore. Since the salt is usually stored together with the user principal, it would be easier to select the property used as salt by annotating it, without having to override the IdentityStore component. Using a randomly generated salt is a generally accepted practice, so it should also be possible to generate the salt value automatically when creating the user via IdentityManager's API. Suggestion: A new annotation, UserPasswordSalt, to annotate property used as salt. Attributes: * generate=true|false -- whether to generate random value * length=salt length in bits (used when generate=true) Example usage: class User { @UserPasswordSalt(generate=true, length=64) String getSalt() {..} @UserPassword(hash="sha1" String getPasswordHash() {...} } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009