Yep, it works now.
Thanks for fix!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126349#4126349
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126349
___
jboss-user mailing l
Ok, there's obviously a misunderstanding as to what is considered to be a
protected page. Rather than drag this out, I've modified the filter to
authenticate every request, regardless of whether there's any security
restrictions on the page or not. Hopefully this should now work for you.
View
I think the use case is slightly different. The way I enabled the HTTP basic
auth is based on the reference doc by editing the components.xml file:
|
|
All pages are protected already with the url-pattern attribute and there is no
additional changes to the pages.xml file or annotation
Try this :D STOP USING RHDS RC1. I had allot of hassle with that thing to.
Download Eclipse WTP and JBOss TOOLS.. good luck
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125385#4125385
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting
Bah, my xml-tags got stripped out of my response. Replace b) with:
b) A element is specified in pages.xml
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125384#4125384
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4
When I say protected, I mean that either:
a) login-required="true" is set in pages.xml
b) A element is specified in pages.xml
or
c) A component method is annotated with @Restrict
As for the silent authentication, look at Identity.hasRole() and
Identity.checkPermission(), both of these methods c
"[EMAIL PROTECTED]" wrote : If you're invoking a restricted method and the
credentials are set (which is what the AuthenticationFilter does) then a silent
login will automatically occur, with no need to explicitly call
Identity.authenticate(). Digest authentication is a special case, with a
sp
If you're invoking a restricted method and the credentials are set (which is
what the AuthenticationFilter does) then a silent login will automatically
occur, with no need to explicitly call Identity.authenticate(). Digest
authentication is a special case, with a special type of authenticator.
"[EMAIL PROTECTED]" wrote : The authentication should be triggered when
calling/accessing a restricted Seam component, doing the chain.doFilter() call.
It can't happen in the filter as not all contexts exist at that point in time.
My point might not be right as I am not as familiar to the frame
The authentication should be triggered when calling/accessing a restricted Seam
component, doing the chain.doFilter() call. It can't happen in the filter as
not all contexts exist at that point in time.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125325#4
"[EMAIL PROTECTED]" wrote : This should be fixed in CVS now, please let me know
if there's any further issues with HTTP authentication.
Has this been tested? Because when I look at the code in the latest trunk, I
didn't see any code that would fix the second problem I mentioned (see the
"Proble
This should be fixed in CVS now, please let me know if there's any further
issues with HTTP authentication.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124982#4124982
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41
As promised, the JIRA issue:
http://jira.jboss.com/jira/browse/JBSEAM-2558
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124924#4124924
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124924
I had a look at the code for AuthenticationFilter.processBasicAuth(). It
actually looks like Identity is not being found in the context:
private void processBasicAuth(HttpServletRequest request,
| HttpServletResponse response, FilterChain chain)
| throws IOException, Se
14 matches
Mail list logo
