Turns out there is a small problem with K2 caching of AD users in a multi-domain environment. A fix should be included in the next release of blackpearl. The work-around in the interim is to turn off caching by:
Changing the 'ADCache' value in the RoleInit column of the security label to 0 (the default is 10).
For example:
"<roleprovider><init>ADCache=0;LDAPPath=LDAP://DC=K2DEMO,DC=LOCAL;..."
This will force K2 to always query AD rather than using the cache.
Technorati Tags: K2 blackpearl
0 comments:
Post a Comment