[JBoss JIRA] Created: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
4:14 p.m.
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
4:26 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin updated JBSEAM-4674:
----------------------------------
Summary: Secured resources does not work with RESTEasy and seam
2.2.1-SNAPSHOT : 403 returned (was: Secured resources does not work with RESTEasy and
seam 2.2.1-SNAPSHOT)
Description:
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 403 http code, unauthorized.
Switch to seam 2.2.0 without changing anything else makes the secured resource work as
expected.
was:
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.
Steps to Reproduce:
Try to access a secured resource
Log in
=> 403 error returned.
was:
Try to access a secured resource
Log in
=> 401 error returned.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
4:28 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin commented on JBSEAM-4674:
---------------------------------------
I've tried with updated RESTeasy jars from the 2.0.0.GA release : same thing.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
4:34 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin commented on JBSEAM-4674:
---------------------------------------
More information from the logs :
2010-07-22 16:31:48,462 DEBUG [org.jboss.seam.servlet.ContextualHttpServletRequest]
beginning request
2010-07-22 16:31:48,462 DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>>
Begin web request
2010-07-22 16:31:48,462 DEBUG [org.jboss.seam.core.Manager] No stored conversation
2010-07-22 16:31:48,463 DEBUG [org.jboss.seam.resteasy.ResteasyResourceAdapter] processing
REST request
2010-07-22 16:31:48,463 DEBUG [org.jboss.seam.servlet.ContextualHttpServletRequest]
beginning request
2010-07-22 16:31:48,463 DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>>
Begin web request
2010-07-22 16:31:48,463 DEBUG [org.jboss.seam.core.Manager] No stored conversation
2010-07-22 16:31:48,464 DEBUG [org.jboss.seam.resteasy.ResteasyResourceAdapter] Using
request mapping prefix: /seam/resource/restv1
2010-07-22 16:31:48,465 DEBUG [org.jboss.resteasy.core.SynchronousDispatcher] PathInfo:
/test/1
2010-07-22 16:31:48,465 DEBUG [org.jboss.seam.resteasy.SeamResteasyResourceFactory]
creating RESTEasy resource instance by looking up Seam component: restApi
2010-07-22 16:31:48,465 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state:
12
2010-07-22 16:31:48,465 DEBUG [org.jboss.seam.contexts.ServletLifecycle] After request,
destroying contexts
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying business
process context
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying conversation
context
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.bpm.businessProcess
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] flushing server-side
conversation context
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] flushing session context
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying event context
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.core.conversationPropagation
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
com.exade.vcp.Filter.done
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.ajax4jsf.webapp.BaseFilter:MyFacesFilterChecked
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.transaction.transaction
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.resteasy.core.ResourceMethod
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.core.manager
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.web.servletContexts
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.seam.core.events
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.resteasy.spi.HttpRequest
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying: restApi
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
com.exade.vcp.Filter.ResponseWrapper
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Contexts] destroying:
org.jboss.resteasy.spi.HttpResponse
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.ServletLifecycle] <<< End
web request
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.servlet.ContextualHttpServletRequest] ended
request
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.resteasy.ResteasyResourceAdapter] completed
processing of REST request
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Lifecycle] After request,
destroying contexts
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web
request
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.servlet.ContextualHttpServletRequest] ended
request due to exception
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.servlet.ContextualHttpServletRequest] ended
request
2010-07-22 16:31:48,466 DEBUG [org.jboss.seam.web.ExceptionFilter] handling uncaught
exception
javax.servlet.ServletException: java.lang.IllegalStateException: No active event context
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:75)
at
org.jboss.seam.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:120)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164)
at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141)
at
org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90)
at
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419)
at
org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:378)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: No active event context
at org.jboss.seam.core.Manager.instance(Manager.java:368)
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:56)
... 45 more
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.web.ExceptionFilter] exception root cause
java.lang.IllegalStateException: No active event context
at org.jboss.seam.core.Manager.instance(Manager.java:368)
at
org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:56)
at
org.jboss.seam.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:120)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164)
at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141)
at
org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90)
at
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419)
at
org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:378)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508)
at java.lang.Thread.run(Thread.java:619)
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.web.ExceptionFilter] running exception
handlers
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.contexts.Lifecycle] After request,
destroying contexts
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web
request
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.contexts.FacesLifecycle] >>> Begin
exception recovery
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.core.Manager] No stored conversation
2010-07-22 16:31:48,467 DEBUG [org.jboss.seam.exception.DebugPageHandler] redirecting to
debug page
There is more but I think the useful part is there.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
9:34 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Ray Soto commented on JBSEAM-4674:
----------------------------------
Feedback from end user, this does work with 2.2.1-SNAPSHOT, i currently have it deployed
on development servers. It will however fail to work if debug is set to true. When debug
is disabled in components.xml (and no jboss-seam-debug.jar) is included in archive, this
works without issue.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
9:48 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin commented on JBSEAM-4674:
---------------------------------------
Ah, thank you for the information !
I guess I can use that trick meanwhile. I hope it will be considered for the final release
though.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
3:22 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin commented on JBSEAM-4674:
---------------------------------------
I've updated to svn revision 13629 and it works now, even with debug enabled. Thanks
to whoever fixed it!
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
3:24 p.m.
New subject: [JBoss JIRA] Resolved: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Gaël Beaudoin resolved JBSEAM-4674.
-----------------------------------
Resolution: Done
Fixed in latest 2.2 branch.
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
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 403 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
10:01 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://jira.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugin....
]
Jozef Hartinger updated JBSEAM-4674:
------------------------------------
Assignee: Jozef Hartinger
Component/s: WS
(was: Remoting)
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
Key: JBSEAM-4674
URL: https://jira.jboss.org/browse/JBSEAM-4674
Project: Seam
Issue Type: Bug
Components: WS
Affects Versions: 2.2.1.CR1
Environment: JBoss 4.2.3
Seam 2.2.1-SNAPSHOT
Reporter: Gaël Beaudoin
Assignee: Jozef Hartinger
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 403 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
9:43 p.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-4674) Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT : 403 returned
[
https://issues.jboss.org/browse/JBSEAM-4674?page=com.atlassian.jira.plugi...
]
Marek Novotny closed JBSEAM-4674.
---------------------------------
closing as cleanup
Secured resources does not work with RESTEasy and seam 2.2.1-SNAPSHOT
: 403 returned
------------------------------------------------------------------------------------
Key: JBSEAM-4674
URL: https://issues.jboss.org/browse/JBSEAM-4674
Project: Seam 2
Issue Type: Bug
Components: WS
Affects Versions: 2.2.1.CR1
Environment: JBoss 4.2.3
Seam 2.2.1-SNAPSHOT
Reporter: Beaudoin Gaël
Assignee: Jozef Hartinger
Labels: resteasy, seam
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 403 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4716
days inactive
5088
days old
9 comments
4 participants
participants (4)
-
Gaël Beaudoin (JIRA) -
Jozef Hartinger (JIRA)
-
Marek Novotny (JIRA)
-
Ray Soto (JIRA)