[seam-issues] [JBoss JIRA] Updated: (SEAMSECURITY-67) security-openid-rp/op examples fail with 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed

[ https://issues.jboss.org/browse/SEAMSECURITY-67?page=com.atlassian.jira.p... ] Marek Schmidt updated SEAMSECURITY-67: -------------------------------------- Fix Version/s: Future Environment: JBossAS 6.1.0-SNAPSHOT+Weld 1.1.1, Seam Security 3.0.1-SNAPSHOT (was: JBossAS 6.1.0-SNAPSHOT+Weld 1.1.1) Steps to Reproduce: 0. add www.openid-op.com and www.openid-rp.com as hostnames for 127.0.0.1 in /etc/hosts (as per readme files in the examples) 1. deploy the security-openid-rp and security-openid-op examples 2. go to http://www.openid-rp.com:8080/security-openid-rp/Index.jsf 3. select Custom and put http://www.openid-op.com:8080/security-openid-op/openid/OP/XrdsService to the Custom OpenID URL 4. write "user" as a username (or whatever), click login 5. write "user(a)example.com" as an email (or whatever), click OK 6. notice the error "HTTP Status 400 - 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed" was: 0. Fix SEAMSECURITY-44 in openid-op by renaming org.jboss.seam.security.examples.openid.Identity to @Named("oidentity"), replace "identity" with "oidentity" in all openid-op/src/main/webapp/*.xhtml 1. deploy the security-openid-rp and security-openid-op examples 2. go to http://www.openid-rp.com:8080/security-openid-rp/Index.jsf 3. select Custom and put http://www.openid-op.com:8080/security-openid-op/openid/OP/XrdsService to the Custom OpenID URL 4. write "user" as a username (or whatever), click login 5. write "user(a)example.com" as an email (or whatever), click OK 6. notice the error "HTTP Status 400 - 0x100: Namespace declaration for extension http://openid.net/srv/ax/1.0 MUST be signed" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira