Hi!
Sounds like wicket is redirecting to the login page due to the user not being authenticated. To handle cross-framework authorization, I suggest you either share the http session, use a shared security framework (e.g. apache shiro) or (what we do every now and then) have a shared list of one-time-tokens so you can forward to wicket with that token and wicket can fetch the user based on the token. In any case, can you debug the code? If you set some breakpoint I think you’ll figure out quickly where the problem lies :-) Good luck. Met vriendelijke groet, Kind regards, Bas Gooren Op 10 september 2018 bij 20:01:31, extraquoo (extraq...@gmail.com) schreef: the purpose is the clients want to reuse an existing wicket html page for some enhancement in a spring mvc flow of business. br/>I am ttrying three ways "redirect:../[url]" , "redirect:[url]" and "/[url]" .The first two just kicks me out and return to the application home page which is coded by wicket. The last one is throwing stack trace of apache tiles which is used by spring mvc/spring web flow. you are right, the wicket owns authentication functionality when a user logins the application. Maybe this is the root cause of kick out. Not sure if it could pass the entire session of authentication by some additional code or config file ? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
