What is best way to integrate NTLM with Wicket authentication module ?
Currently, we are migrating from Standard Login page implementation to a
JCIF's NTLM (Windows domain credentials).
JCIF's provides a convenient servlet filter to do the NTLM handshake. It
sticks the username in the HttpServlet.getRemoteUser(). The current
implementation of the wicket is to extend AuthenticatedWebSession and
provide a MyAppWebSession authenticate method and a login page.
@Override
protected Class<? extends WebPage> getSignInPageClass()
{
return LoginPage.class;
}
@Override
protected Class<? extends AuthenticatedWebSession> getWebSessionClass()
{
return MyAppWebSession.class;
}
public class MyAppWebSession extends AuthenticatedWebSession
{
public boolean authenticate(String userName, String password)
{
// This is not the NTLM authentication, i need to get the username
provided
by NTLM here
myAuthenticator.authenticate(username)
}
}
How does wicket determine to show a login-page in the Wicket Application ?
Seems like it's not using getHttpServletRequest().getRemoteUser()
There seems to be a couple of ways to tackle this issue :
1. Use wicket's IAuthorizationStratergy and plugin NtlmAuthenticator (from
JCIF's) into this and add the additional authentication to it.
2. Use Swarm authentication framework.
3. Propagate the username from getHttpServletRequest().getRemoteUser() to
MyAppWebSession class and not show login page if JCIF's filter authenticates
the user using NTLM.
Any pointers/ideas are appreciated,
Ravi
--
View this message in context:
http://www.nabble.com/Wicket-NTLM-Single-sign-on-integration-Question-tp17868669p17868669.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
