On Jul 22, 2008, at 1:27 PM, Ashwill, Steve (Facilities & Services)
wrote:
I'm afraid your about 3 steps ahead of me.
1. Are you running from within a Jetspeed installation under Tomcat
Yes
2.Is your custom login module placed under the jetspeed webapp?
If you mean the portal that I'm using to call the loginContext, then
yes
it is. Perhaps a problem lies in this part?
no, is the correct place
3.Recommend building your login module as a jar...
Will this jar simply contain MyLoginModule.class?
yes, and any other support classes
Or do I need to add something to the manifest?
shouldn't
4.dropping it into the jetspeed WEB-INF/lib directory Is this the same
directory that contains jetspeed-security-2.1.3.jar?
yes
As of right now it does not find it there. It will only find it if I
place MyLoginModule.class in common or shared.
But then your LoginModule won't be able to find any Jetspeed classes
I have placed my login.conf in the webapps\fsportal\WEB-INF\classes
folder
fssoaAuth {
org.apache.jetspeed.security.impl.MyLoginModule required debug=true;
};
5.Then update your Spring configuration (security-atn.xml) to point to
your login module proxy impl Does this look right?
Not sure. Does your "MyLoginModule" implement LoginModuleProxy like
ours:
public class LoginModuleProxyImpl implements LoginModuleProxy
Jetspeed is configured to use its own login module: DefaultLoginModule
(also found in the jetspeed-security jar)
It is configured in login.conf, which is packaged in the jetspeed-
security.jar:
Jetspeed {
org.apache.jetspeed.security.impl.DefaultLoginModule required;
};
