We are using TWiki with SSO-authentication, and the email address as login. For the user mapping, we use TWiki::Users::TWikiUserMapping. User mapping in the RCS comment field (tag on top of the page after save), is messed up with TWiki release 4.2.4 (and other 4.2.x releases.) Instead of "Wikiname" (E.g.
) as user tag in the RCS checkin comments, we get a 7-bit ascii string, like:
. However, the page signature is generated correctly as "Main.Wikiname", e.g.
With 4.1.2, all edited topics are saved correctly, with the wikiname (e.g. NilsHoeimyr) in the signature and in the page annotation for RCS. The setup of filters in LocalSite
.cfg is the same in both installations.
To me, this looks like a bug in 4.2.x, where the mapping of wikiname to RCS fails when email address used as login. (cUID to wikiname error?)
- 15 Dec 2008
I am not sure, but this looks like (yet another) spec change in TWiki. TWiki:TWiki04x02/TWikiReleaseNotes04x02
has this: "The User Mapping system has been further rearchitected to reduce its dependance on the traditional TWiki User topic based management and mapping implementation. TWiki is now capable of dealing with login names that are not 7bit ascii (by transforming those logins into a 'cUID' that can be used by rcs)."
Personally I do not understand why we need a spec change from WikiName RCS user to unreadable 7-bit ASCII RCS user. If login to an account is possible with multiple names (such as multiple e-mail addresses) those would recorded as different cuids, even though it is the same user.
- 21 Jan 2009
I first believed that the bug was gone in TWiki 4.3, but later found out that this bug depends on the "password manager" setting. If the "password manager" is set to "none" and login manager is set to Apache Login, the RCS user string is garbled. If the password manager remains the default TWiki password manager, the RCS user string is correct! As we use the Apache Login manager with SSO, the login manager should be set to none. (Please note that the bug is not present in Foswiki 1.0. or 1.0.4).
- 07 Apr 2009
Could you check if this is related to Item6250
- 16 Apr 2009
No is not fixed.
I think that is the same problem like:
- 10 Jul 2009