Hi
2010/9/6 Elisabeth Adler
> Hi all,
>
> I am currently facing a nasty issue that is haunting me for the past couple
> of days. When a user tries to access a specific URL he should be forwarded
> to the login page. This was working before (Tapestry 5.0.11) but after
> switching to 5.0.19 it is
Well, that did help. Somehow, as it left me even more confused at the
beginning. Debugging activated, I came to realize, that the
loadByUsername method in the UserDetailsServiceImpl never even is called
on Login.
So, knowing that I started to mock around in the AppModule and pushed
things aro
My advice is to debug your application to check if the password encoding at
login time is the same as the one you provided at creation time.
Put a break point in the method that retrieves the user from DB, have a look
the stack in eclipse debug mode, identifiy the Authentication Spring Filter,
go
The way I encode the password is using the following create method in
UserServiceImpl:
...
public UserServiceImpl(PasswordEncoder encoder, SaltSource salt, UserDAO
userDao, Logger logger, IRoleService roleService) {
this.encoder = encoder;
this.salt = salt;
this.userDao
Have you checked that the encoder used by Spring filter is the same you use
to encode it in your DB ?
Password Encoding is made of a salt and an algorithm.
2010/6/10 Daniel Henze
> Thanks for your reply.
>
> Yes, I did check that. And it's ok, lovely long and encrypted passwords.
>
> Daniel
>
Thanks for your reply.
Yes, I did check that. And it's ok, lovely long and encrypted passwords.
Daniel
Am 10.06.2010 09:51, schrieb Christophe Cordenier:
Hi
I guess you already did it but have you checked if the password is stored in
SHA1 ?
2010/6/10 Daniel Henze
Hi there,
I installed
Hi
I guess you already did it but have you checked if the password is stored in
SHA1 ?
2010/6/10 Daniel Henze
> Hi there,
>
> I installed Tapestry-Spring-Security and followed the installation and
> configuration advise. But I have no luck as the login does not work for me
> and always returns
On Mon, Jul 13, 2009 at 7:15 PM, Sergey Didenko wrote:
> Is it true that the only ways to have "remember me" feature for
> authentication are
>
> 1) to use spring security
> 2) to implement it manually (and call it in Dispatcher or RequestFilter)
>
> As I understand chenillekit-access does not sup
Ahhh, just as I wanted to go home after deploying the app to the
tomcat server and baaammm - the app crashes. So if it works on Jetty
6.1.14 and crashes on Tomcat 6.0.14, can the web.xml be the bad guy? I
am using T5.0.18
http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://java.sun.com/xml/
Found a solution. The login is now protected as google account is -
with captcha after 5 failed retries.
The thing that bothers me is this stack trace in the console which is
triggered by pressing the login submit button:
2009-03-26 16:44:51.494::WARN: /login.lform
java.lang.NullPointerException
Ups, that was beers :-)
2009/1/23 Borut Bolčina
> 100 bears for Ulrich!
>
> It works. You made my day. Thanks,
>
> -Borut
>
> 2009/1/23 Ulrich Stärk
>
> Hi Borut,
>>
>> the problem was that both the OpenIdProcessingFilter and the filter used
>> for form-based authentication both were configured
100 bears for Ulrich!
It works. You made my day. Thanks,
-Borut
2009/1/23 Ulrich Stärk
> Hi Borut,
>
> the problem was that both the OpenIdProcessingFilter and the filter used
> for form-based authentication both were configured for the same url, namely
> spring-security.check.url. Therefore b
Hi Borut,
the problem was that both the OpenIdProcessingFilter and the filter used
for form-based authentication both were configured for the same url,
namely spring-security.check.url. Therefore both filters tried to
process the credentials entered, which had to fail. I updated the wiki
arti
Hello,
today I first read the documentation for the tapestry ioc - it took me
several hours. I am still not at a point where "I got it" as Howard really
well described at
http://tapestry.apache.org/tapestry5/tapestry-ioc/overview.html. This
introductory doc is really good!
I downloaded the tapest
Normally, authentication providers are called in order (as in:
OrderedConfiguration). I've never tried using
OpenID, though.
> -Original Message-
> From: Borut Bolčina [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 25, 2008 10:32
> To: Tapestry users
> Subject
Regards,
Borut
2008/11/25 Jonathan Barker <[EMAIL PROTECTED]>:
>
> It's ugly, but you could build one of the two UserDetailServices in the
> contributeProviderManager method, so only one UserDetailsService is visible
> to the RememberMe s
25, 2008 07:29
> To: Tapestry users
> Subject: Re: Authentication
>
> Hi,
>
> only now have I returned to this task. I get http error 500:
>
> Exception constructing service 'RememberMeServices': Error invoking
> service builder method
> nu.localhost.tapestr
Hi,
only now have I returned to this task. I get http error 500:
Exception constructing service 'RememberMeServices': Error invoking
service builder method
nu.localhost.tapestry5.springsecurity.services.SecurityModule.build(UserDetailsService,
String) (at SecurityModule.java:303) (for service
'Re
Personally, I stick to using a stateful session bean, but I also provide
single sign on for my various web apps. I've also used the standard J2EE's
j_username and j_password with an LDAP realm.
Both have nothing to do with Tapestry, but still apply.
(Just my 2 cents)
On Thu, Nov 6, 2008 at 5:06
Thanks Ulrich! I will try that first thing Monday morning as I am going on a
short vacation in a few hours. This method signature looks pretty scary as I
am not used to this kind of syntax yet.
Cheers,
Borut
2008/11/6 Ulrich Stärk <[EMAIL PROTECTED]>
> Just inject both providers into your contri
Just inject both providers into your contributeProviderManager method:
public static void contributeProviderManager(
OrderedConfiguration configuration,
@InjectService("OpenIDAuthenticationProvider")
AuthenticationProvider openIdAuthenticationProvider,
@InjectServi
Hi Gabriel
I have a similar setup using a JDBC realm as well as multiple
applications running on the domain so the best solution for me was to
look for the authorization header in the browser and use this info to
authenticate
Chris posted a great wiki article on how to implement a Dispatcher
Peter Stavrinides a écrit :
Hi all
My question is more of a best practice related question, I want to use
a filter to extract my authentication code from the rest of the
application logic, [...]
Thanks in advance,
Peter
Hi,
First, I'm a real Tapestry newbie, and I believe that Tapestry has
From
http://tapestry.apache.org/tapestry5/tapestry-core/guide/lifecycle.html:
"This is how Tapestry keeps you from worrying about multi-threading
issues ... the objects involved in any request are reserved to just that
request (and just that thread)."
So I think you are right. Let me amend
Hi Chris,
You wrote:
manager to retrieve page members marked as state objects with the
@ApplicationState annotation. Why? Because an instance of a page class
may be accessed simultaneously by many different requests at the same
time. In reality the annotation is just an indicator that a page
will do!
Peter
Chris Lewis wrote:
Actually by indirection it is also my problem ;-), and I'd like to
know if you find this not to be true. I have done some digging and
chatting (on this list) about this topic, and for all I've found this
appears to be how it is designed. As such I shape my id
Actually by indirection it is also my problem ;-), and I'd like to know
if you find this not to be true. I have done some digging and chatting
(on this list) about this topic, and for all I've found this appears to
be how it is designed. As such I shape my ideas and plans around this
understand
Hi Chris,
Thanks for the clarification, this is what I had initially thought...
however some quick and dirty tests made me doubt this, I am not sure why
it didn't turn up for me that way, I will have to check my code again
... not your problem anyway.
Thanks again,
Peter
Chris Lewis wrote:
Hi Peter,
I'll ask Howard to verify what I say here as its a pretty important
issue. Short answer: Yes, you will get the same instance using the state
manager as you would from injection via @ApplicationState... for
simultaneous requests made by the same user (and therefore the same
request/s
Hi Chris,
Thanks for the great wiki article, I have managed to implement what I
needed using 'Tapestry5HowToCreateADispatcher2'. My implementation is
very similar to the example... it seems to work great!
One question though regarding my ASO (which is similar to your
permissions ASO), you me
Hi Chris
Yes, this is kind of what I am looking for, I will give it a go...
Thanks
Peter
Chris Lewis wrote:
Hello Peter,
It sounds like by 'filter' you mean a servlet filter and not a
Tapestry filter. Your requirements sound a tad exotic to me, but these
wikis should get you on the right tr
Hello Peter,
It sounds like by 'filter' you mean a servlet filter and not a Tapestry
filter. Your requirements sound a tad exotic to me, but these wikis
should get you on the right track:
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher
http://wiki.apache.org/tapestry/Tapestry5
32 matches
Mail list logo
