Hello I have some trouble with my next wicket application. I want to create a new ecommerce application. I have the store and the admin parts. Initial, the store and admin parts are two distinct (maven) modules and two distinct application (war files) but I realize that it's hard to develop new extensions with this approach. Now, I want to merge the store and admin applications in one big application but I have some problems. First my big problem is Authentication section (with wicket-auth-role) because I have in store section the Customer objects with the pair emaiAddress/password and in admin section I use User objects with the pair username/password. My Session extends AuthenticatedWebSession with an AuthenticationManager injected by spring. For page protection I use @AuthorizeInstantiation. I use this annotation to protect both store and admin pages. The problem is that AuthenticatedWebApplication.getSignInPageClass returns one Login page and I have two Login pages (one for store pages and one for admin pages). What it's the best approach for this kind of wicket application with frontend and backend require some authentication (security) but "user" entities are not the same (complete distinct tables in database)?
Any advice is welcome, Thanks Decebal -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/need-some-advice-tp3619252p3619252.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
