July 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4126) Danish messages for seam-gen

by Viktor Rasmussen (JIRA)

Danish messages for seam-gen ---------------------------- Key: JBSEAM-4126 URL: https://jira.jboss.org/jira/browse/JBSEAM-4126 Project: Seam Issue Type: Patch Components: Tools Reporter: Viktor Rasmussen Priority: Optional This is the messages_en.properties file translated into danish -- 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

13 years, 9 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3213) Support other content than UIOuput children in Excel datatable-exporter

by Nicklas Karlsson (JIRA)

Support other content than UIOuput children in Excel datatable-exporter ----------------------------------------------------------------------- Key: JBSEAM-3213 URL: https://jira.jboss.org/jira/browse/JBSEAM-3213 Project: Seam Issue Type: Feature Request Components: Excel Reporter: Nicklas Karlsson Currently, the Excel exporter looks for UIOutput children of UIColumns for export. Add support for plain text/EL expressions also -- 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

13 years, 9 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3142) Maven dependency on jboss-seam not defined properly

by Thomas Diesler (JIRA)

Maven dependency on jboss-seam not defined properly --------------------------------------------------- Key: JBSEAM-3142 URL: http://jira.jboss.com/jira/browse/JBSEAM-3142 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.GA Reporter: Thomas Diesler jboss-seam-ioc http://repository.jboss.com/maven2/org/jboss/seam/jboss-seam-ioc/2.0.2.GA... defines the dependency on jboss-seam like this <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> </dependency> However, jboss-seam uses packaging 'ejb' http://repository.jboss.com/maven2/org/jboss/seam/jboss-seam/2.0.2.GA/jbo... <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <parent> <groupId>org.jboss.seam</groupId> <artifactId>parent</artifactId> <version>2.0.2.GA</version> </parent> <packaging>ejb</packaging> The dependency should be defined like this <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <type>ejb</type> </dependency> If this is not done correctly, modules that depend on jboss-seam type 'ejb' directly need to exclude the incorrectly defined dependency <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam-ioc</artifactId> <exclusions> <exclusion> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> </exclusion> </exclusions> </dependency> -- 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

13 years, 9 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3972) identity login security bug

by David Croe (JIRA)

identity login security bug --------------------------- Key: JBSEAM-3972 URL: https://jira.jboss.org/jira/browse/JBSEAM-3972 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.1.GA Environment: jboss 4.2.3. Reporter: David Croe Hello ! I think there is a major security bug in the seamspace example, which will give a user the permissions of the user which has been logged in before. To reproduce the scenario: 1. login in as user demo. 2. click the back button or enter the login page manually in the url of your browser 3. login as another user. the second user will have the admin permissions of the demo user! Problem is that the authenticate method will not be invoked if you are allready logged in ( even as another user) and the old principal with the assigned permissions will stay in memory. Greetings D.Croe -- 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

13 years, 10 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3941) IdentityMaanger: extend permission checks to allow user to modify his own password

by Raimund HÃÂ¶lle (JIRA)

IdentityMaanger: extend permission checks to allow user to modify his own password ---------------------------------------------------------------------------------- Key: JBSEAM-3941 URL: https://jira.jboss.org/jira/browse/JBSEAM-3941 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1 Reporter: Raimund HÃÂ¶lle Priority: Minor Because IdentityManager.changePassword() requires the permission ("seam.user", "update"), it is not possible to use that method to change the password of the authenticated user itself without granting that permission to him. But granting that means, the user is able to modify _any_ user. I'm suggest to add a new permission target (or maybe a new action) and extend the changePassword() method: public static final String OWNPASSWORD_PERMISSION_NAME = "seam.user.ownpassword"; public boolean changePassword(String name, String password) { Identity identity = Identity.instance(); try { identity.checkPermission(USER_PERMISSION_NAME, PERMISSION_UPDATE); } catch (AuthorizationException e) { if ( identity.isLoggedIn() && identity.getCredentials().getUsername().equals(name) ) { Identity.instance().checkPermission(OWNPASSWORD_PERMISSION_NAME, PERMISSION_UPDATE); } else { throw e; } } return identityStore.changePassword(name, password); } Or maybe a specialized method? Many regards, Raimund -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-15) Investigate options for deprecating IdentityManager

by Shane Bryzak (JIRA)

Investigate options for deprecating IdentityManager --------------------------------------------------- Key: SEAMSECURITY-15 URL: https://jira.jboss.org/browse/SEAMSECURITY-15 Project: Seam Security Issue Type: Feature Request Reporter: Shane Bryzak Assignee: Shane Bryzak One way we can most likely achieve this is by providing a set of action beans (similar to the existing RoleAction/RoleSearch and UserAction/UserSearch beans). Security checks for the identity management related operations can be expressed by placing security annotations on the bean's corresponding methods, and the bean would also be responsible for transaction control and providing a persistence context where required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-23) Add exception handling

by Jason Porter (JIRA)

Add exception handling ---------------------- Key: SEAMFACES-23 URL: https://jira.jboss.org/browse/SEAMFACES-23 Project: Seam Faces Issue Type: Feature Request Reporter: Jason Porter Fix For: 3.0.0.Alpha3 Create exception handling integration similar to what Seam 2 had. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-5) Proxy @PersistenceContext injected EntityManager so that they can use EL in queries

by Stuart Douglas (JIRA)

Proxy @PersistenceContext injected EntityManager so that they can use EL in queries ----------------------------------------------------------------------------------- Key: SEAMPERSIST-5 URL: https://jira.jboss.org/browse/SEAMPERSIST-5 Project: Seam Persistence and Transactions Issue Type: Feature Request Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-3) Support managed hibernate session

by Stuart Douglas (JIRA)

Support managed hibernate session --------------------------------- Key: SEAMPERSIST-3 URL: https://jira.jboss.org/browse/SEAMPERSIST-3 Project: Seam Persistence and Transactions Issue Type: Feature Request Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4452) Enable LdapIdentityStore to access LDAP via SSL

by Marco Brizi (JIRA)

Enable LdapIdentityStore to access LDAP via SSL ----------------------------------------------- Key: JBSEAM-4452 URL: https://jira.jboss.org/jira/browse/JBSEAM-4452 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA Environment: Ubuntu 9.04, JBoss AS 5.1.0 GA Reporter: Marco Brizi The current LdapIdentityStore offers a good support for integrate an LDAP repository. Unfortunately, at the moment, there is no configuration to access it via SSL. The minimum support could be done by adding a new boolean attribute (for ex. ssl-enabled) in the ldap-identity-store element to offer the possibility to choose or not a secure communication. I've tried to implement this extension changing security-2.2.xsd and the LdapIdentityStore class. In the second file my work has been on new attribute getter/setter and on initialiseContext(String principal, String credentials) method just adding the following lines : String ldapProtocol = "ldap"; if (isSslEnabled()) { ldapProtocol = "ldaps"; env.setProperty(Context.SECURITY_PROTOCOL, "ssl"); } String providerUrl = String.format("%s://%s:%d", ldapProtocol, getServerAddress(), getServerPort()); In addition get the server certificate and set the -D/usr/lib/jvm/java-6-sun=/path/to/keystore as JAVA_OPTS is needed. At the moment I'm able to initiate the communication with secure LDAP server but the Identity.authenticate causes a "javax.security.auth.login.LoginException: Login Failure: all modules ignored" The complete stacktrace is attached to the issue. -- 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

13 years, 10 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2010