Laura,
The stack trace you provided *does* appear to be caused by the absence of a '
user.login.id' attribute.
I'm looking at the GatewayPortlet code here:
http://toro-portlets.googlecode.com/svn/trunk/academus-apps/source/net/unicon/academus/apps/gateway/GatewayPortlet.javaHere's line 96 (the one that's crashing):
*****
private String constructUserContextCacheKey(PortletSession session,
String username) {
// put the username first, so we can be assured of parsing it out later
(96) StringBuffer sb = new StringBuffer(username).append('/');
sb.append(id).append('/');
sb.append(session.getId());
return sb.toString();
}
*****
And here's line 235 (the lone that's calling the method that crashes):
*****
// Look for existing, create if we don't find.
GatewayUserContext rslt = (GatewayUserContext) s.getAttribute(key);
if (rslt == null) {
String username = (String)userInfo.get("
user.login.id");
(235) String cacheKey = constructUserContextCacheKey(s, username);
[...]
*****
To verify that your LDAP user has a '
user.login.id' attribute, use the Groups Manager channel; search for a Person and enter your username. Click on the match to see the person's attributes. If you don't see '
user.login.id' you need to open personDirectory.xml and configure a value for it.
drew wills