April 2011 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1229) Remoting exception with JMS subscription

by Alex Mateescu (JIRA)

Remoting exception with JMS subscription ---------------------------------------- Key: JBSEAM-1229 URL: http://jira.jboss.com/jira/browse/JBSEAM-1229 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA Environment: JEMS Installer 1.2 ejb3 profile, JBoss Portal 2.6.0ALPHA1, JBoss Seam 1.2.1GA running on Fedora Core 6, Firefox 1.5 Reporter: Alex Mateescu Assigned To: Shane Bryzak Priority: Minor I am deploying an EAR with multiple (the number is probably irrelevant) JARs and WARs that use Seam Remoting and subscribe to a JMS topic. The subscribe calls work fine, they send the correct topic name and receive a token. On the first poll, though, there is an exception: 2007-04-23 14:08:29,602 ERROR [org.jboss.seam.remoting.Remoting] Error java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context. [undefined] at org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:179) at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:45) at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:83) at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:110) at org.jboss.seam.servlet.ResourceServlet.doGet(ResourceServlet.java:68) at org.jboss.seam.servlet.ResourceServlet.doPost(ResourceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) Upon closer inspection, the polling request looks like this: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="undefined" timeout="10"/></body></envelope> which is the cause of the exception. Subsequent calls look fine: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="3922899d-1e6b-4bc1-96ab-3713f4460446" timeout="10"/></body></envelope> I think the error was there before, when using Seam 1.1.0GA, but it was random. I may be wrong, but now it is always there. Of course, remoting works fine after the initial call. -- 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, 5 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3219) Describe JAAS integration more in depth in the docs

by Samuel Mendenhall (JIRA)

Describe JAAS integration more in depth in the docs --------------------------------------------------- Key: JBSEAM-3219 URL: https://jira.jboss.org/jira/browse/JBSEAM-3219 Project: Seam Issue Type: Task Components: Security Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1 Reporter: Samuel Mendenhall Priority: Minor Add more documentation detailing the integration with Seam Identity and JAAS and what integration is included and what is not. For example, discuss logging in with the container's JAAS configuration via <security:identity jaas-config-name="other"/> and the integration or lack thereof with the EJB3 container as a result of doing that. -- 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, 5 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3886) Document the usage of <web-identity-filter disabled="true"> to disable identity managment

by Denis Forveille (JIRA)

Document the usage of <web-identity-filter disabled="true"> to disable identity managment ----------------------------------------------------------------------------------------- Key: JBSEAM-3886 URL: https://jira.jboss.org/jira/browse/JBSEAM-3886 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor Document the usage of <web-identity-filter disabled="true"> to disable identity managment in seam v2.1 as stated in jira JBSEAM-3629 Maybe this should be included in section 15.2 (Security/Disabling security) ? -- 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, 5 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3890) Update the samples to user "credentials" instead of "identity"

by Denis Forveille (JIRA)

Update the samples to user "credentials" instead of "identity" -------------------------------------------------------------- Key: JBSEAM-3890 URL: https://jira.jboss.org/jira/browse/JBSEAM-3890 Project: Seam Issue Type: Bug Components: Documentation Issues, Security Affects Versions: 2.1.1.GA Reporter: Denis Forveille Priority: Minor In the security chapters, section 15.3.2 and 15.3.3, the code snippets use the "Credentials" class to store the username and the password of the user that is performing a login. The samples still use the "old" (?) way, ie use the identity class to store this data, at leat for the "blog", "booking", "dvdstore", etc... It seems that not one sample use the "Cedentials" class -- 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, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3942) LdapIdentityStore should crypt password

by Raimund Hölle (JIRA)

LdapIdentityStore should crypt password --------------------------------------- Key: JBSEAM-3942 URL: https://jira.jboss.org/jira/browse/JBSEAM-3942 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 LdapIdentityStore.changePassword() stores the new password always as plain text in the LDAP database. To allow crypted passwords, i suggest the following modifications: New bean properties (along with getter / setter): private String passwordCryptAlgorithm = "SHA"; // Or "" for plain text, "MD5", ... private String passwordEncoding = "UTF-8"; Extend changePassword() by one additional line: public boolean changePassword(String name, String password) { InitialLdapContext ctx = null; try { ctx = initialiseContext(); // crypt password if not already done password = cryptPwIfNeeded(password); BasicAttribute passwordAttrib = new BasicAttribute(getUserPasswordAttribute(), password); New Helpers method: private Pattern cryptedPwRegexp = Pattern.compile("^[{].+[}].+"); private String cryptPwIfNeeded(String password) { // only crypt if requested by algorithm and not already done! if (getPasswordCryptAlgorithm() != null && ! getPasswordCryptAlgorithm().equals("") && ! cryptedPwRegexp.matcher(password).matches()) { try { MessageDigest md; md = MessageDigest.getInstance(getPasswordCryptAlgorithm()); md.reset(); md.update(password.getBytes(getPasswordEncoding())); byte[] result = md.digest(); password = "{" + getPasswordCryptAlgorithm() + "}" + (new BASE64Encoder()).encode(result); } catch ( NoSuchAlgorithmException e ) { throw new IdentityManagementException( "Configuration problem - can not crypt password with algorithm " + getPasswordCryptAlgorithm(), e); } catch ( UnsupportedEncodingException e ) { throw new IdentityManagementException( "Configuration problem - can not encode password with " + getPasswordEncoding(), e); } } return password; } 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, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4427) JpaPermissionStore: Auto-detect discriminator value if rolePermissionClass is set

by Alexander Galanin (JIRA)

JpaPermissionStore: Auto-detect discriminator value if rolePermissionClass is set --------------------------------------------------------------------------------- Key: JBSEAM-4427 URL: https://jira.jboss.org/jira/browse/JBSEAM-4427 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.2.0.GA Reporter: Alexander Galanin Priority: Minor Currently discriminatorValue auto-detected only if rolePermissionClass is null. I propose to modify JpaPermissionStore::initProperties() to allow auto-detection of discriminatorValue if discriminatorProperty is null. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT

by Gaël Beaudoin (JIRA)

Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT --------------------------------------------------------------------- Key: JBSEAM-4674 URL: https://jira.jboss.org/browse/JBSEAM-4674 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.2.1.CR1 Environment: JBoss 4.2.3 Seam 2.2.1-SNAPSHOT Reporter: Gaël Beaudoin Securing resources like this : http://docs.jboss.org/seam/2.2.1.CR1/reference/en-US/html_single/#d0e22406 It works fine with the released seam 2.2.0 (RESTeasy 1.1x) but not with seam 2.2.1-SNAPSHOT (from a few days ago) (RESTeasy 2.0-beta). The authentication works, debugging the application I can see I am logged in, but then seam return a 401 http code, unauthorized. Switch to seam 2.2.0 without changing anything else makes the secured resource work as expected. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4551) iPhone does not show existed PDF attachment in the message

by Oleg Golitsin (JIRA)

iPhone does not show existed PDF attachment in the message ---------------------------------------------------------- Key: JBSEAM-4551 URL: https://jira.jboss.org/jira/browse/JBSEAM-4551 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.1.GA Reporter: Oleg Golitsin Assignee: Pete Muir Here is the simple test example with a pdf attachment: <m:message xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://jboss.com/products/seam/mail" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:p="http://jboss.com/products/seam/pdf" xmlns:c="http://java.sun.com/jstl/core" charset="UTF-8"> <m:header name="X-Sent-From" value="JBoss Seam"/> <m:from name="noreply" address="noreply(a)test.com"/> <m:to address="email(a)test.com"/> <m:subject><h:outputText value="Test msg" /></m:subject> <m:attachment fileName="tiny.pdf"> <p:document> A very tiny PDF </p:document> </m:attachment> <m:body> <p>Test</p> </m:body> </m:message> iPhone shows the paper clip for such message in the list but when the message is open - the attachment is hidden without any way to view it. -- 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, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4326) Allow to specify a directory with rule resources to Seam RuleBase

by Tihomir Surdilovic (JIRA)

Allow to specify a directory with rule resources to Seam RuleBase ----------------------------------------------------------------- Key: JBSEAM-4326 URL: https://jira.jboss.org/jira/browse/JBSEAM-4326 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.CR1 Reporter: Tihomir Surdilovic Currently org.jboss.seam.drools.RuleBase allows to add a list of rule resources individually, for example: -- 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, 5 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4456) Support for reloading classpath security.drl

by Miloslav Vlach (JIRA)

Support for reloading classpath security.drl -------------------------------------------- Key: JBSEAM-4456 URL: https://jira.jboss.org/jira/browse/JBSEAM-4456 Project: Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.2.0.GA Environment: Drools without BRMS Reporter: Miloslav Vlach Attachments: RuleAgent.java.patch.zip I need to enable reloading *.drl files located in classpath. The attribute files load only files typed in absolute path form. <security:rule-based-permission-resolver security-rules="#{ruleAgent}" /> <security:identity authenticate-method="#{authenticator.authenticate}" remember-me="true" /> <drools:rule-agent name="ruleAgent" files="classpath:///security.drl classpath:///security2.drl" local-cache-dir="/tmp/" poll="5"/> <drools:managed-working-memory name="policyPricingWorkingMemory" auto-create="true" rule-base="#{ruleAgent}" /> More info at http://www.bpsolutions.cz/blog/-/blogs/reloadable-drools-jboss-rules-secu... -- 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, 5 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011