Fixed a problem where the identityId was not getting set correctly in
the SessionTokens when a startSearchContext was not being configured.
This commit is contained in:
parent
b36e17ea15
commit
040895e677
@ -276,7 +276,7 @@ public class Authenticate implements RpcMethod
|
||||
// Create response based on the identity resolution results
|
||||
if (identId != null && identId.length() != 0)
|
||||
{
|
||||
System.err.println("Authenticate.invoke()- identId resolved");
|
||||
System.err.println("Authenticate.invoke()- identId resolved, " + identId);
|
||||
|
||||
// An identity was resolved, get a SessionToken for it.
|
||||
SessionToken sessionToken = new SessionToken(identId,
|
||||
|
@ -223,7 +223,14 @@ public class Krb5Authenticate implements AuthMechanism, Serializable
|
||||
{
|
||||
// The search succeeded, set the identity id.
|
||||
SearchResult sr = (SearchResult)answer.next();
|
||||
identId = sr.getName() + "," + m_svcConfig.getSetting(SvcConfig.StartSearchContext);
|
||||
if (searchContext.equals(""))
|
||||
{
|
||||
identId = sr.getName();
|
||||
}
|
||||
else
|
||||
{
|
||||
identId = sr.getName() + "," + searchContext;
|
||||
}
|
||||
}
|
||||
}
|
||||
catch (NamingException e)
|
||||
|
Loading…
Reference in New Issue
Block a user