Never mind... I wasn't calling super.init() when I was overriding init() in SwarmWebApplication impl
-----Original Message----- From: William Hoover [mailto:[EMAIL PROTECTED] Sent: Friday, January 04, 2008 1:14 PM To: users@wicket.apache.org Subject: RE: [wicket-security] LDAP integration? I'm with you... it doesn't seem to be too difficult to get the mapping between ldap/swarm working. I am attempting to try it out in a simple application. However, I am receiving a NullPointerException in WaspSession because the StrategyFactory is not instantiated. Is there something else that needs to be down in the SwarmWebApplication (following the instructions from http://wicketstuff.org/confluence/display/STUFFWIKI/Getting+started+with+Swarm)? public WaspSession(WaspApplication application, Request request) { super(request); securityStrategy = application.getStrategyFactory().newStrategy(); // throws npe } -----Original Message----- From: Maurice Marrink [mailto:[EMAIL PROTECTED] Sent: Friday, January 04, 2008 11:16 AM To: users@wicket.apache.org Subject: Re: [wicket-security] LDAP integration? I think there will be one more beta before we do the final. I recently made some changes to boost performance and a public beta for that will be better. Even though we are already using it in our apps without problems through the snapshot release. With any luck the 2nd beta will be released this weekend and the final will probably follow soon after. Well the slightly more complex route is connecting to ldap yourself (option number 1 in my previous mail). Personally i think the mapping between ldap and swarm will be a breeze. because a swarm principal is basically just a name. Maurice On Jan 4, 2008 3:43 PM, William Hoover <[EMAIL PROTECTED]> wrote: > Thanks for the info. We are not using Spring (opted for Plexus) so I'm not > sure how plausible it will be to implement the easiest solution in our case. > The application in question is still in the preliminary evaluation stage so > we may have to look for another route. > > Do you have a roadmap/timeline on a release date for wicket-security? > > > -----Original Message----- > From: Maurice Marrink [mailto:[EMAIL PROTECTED] > Sent: Friday, January 04, 2008 8:36 AM > To: users@wicket.apache.org > Subject: Re: [wicket-security] LDAP integration? > > > Yes and not exactly. > > wicket-security is build with plugability in mind, meaning if it does > not yet exist you can build it yourself quite easily. > Regarding LDAP, i myself have never worked with it but there are a > couple of options you can try > -use swarm and map ldap permissions to swarm principals > -use swarm with acegi and let acegi handle the ldap part, you still > need to map acegi permissions to swarm principals though but it saves > you from having to do all the ldap connection stuff yourself > -use wasp and build your own ldap implementation, more work but also > more control > > As for the ldap example part, i am afraid you are somewhat on your own. > There is however an example showing how to integrate swarm with acegi > http://wicketstuff.org/confluence/display/STUFFWIKI/Swarm+and+Acegi+HowTo > and there is an other example showing wicket-auth-roles acegi and ldap > http://cwiki.apache.org/WICKET/acegi-and-wicket-auth-roles.html > So if you rip the ldap config from the last example and use it in the > first example instead of the TestingAuthenticationProvider you should > be ready to go > The example also has some suggestion on how you could do your own ldap > permission mapping if you choose to go that way. > > If you decide to go all out and build directly on wasp you should take > a look at swarm itself a a reference, just ignore all the stuff about > permissions, principals, subjects and stuff. > > Maurice > > On Jan 4, 2008 2:15 PM, William Hoover <[EMAIL PROTECTED]> wrote: > > Can wicket-security be used with LDAP? If so, are there any examples > > available demonstrating its use? > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
