OK, if that's an existing method, then I have no problem.  The original
comment on this thread led me to understand that such a method didn't
exist.  End of issue.

On Tue, 2008-06-10 at 19:38 +0300, Janne Jalkanen wrote:

> Try UserProfile.getUid().
> 
> /Janne
> 
> On 10 Jun 2008, at 19:28, Terry Steichen wrote:
> 
> > What I am doing is logging activity on my JSPWiki-based system.  It is
> > extremely important that I am able to keep track the activities of a
> > given user.  Prior to adding the capability to change login name, that
> > was pretty straightforward.  Now it isn't (so, what I had to do in the
> > meanwhile was modify JSPWiki so my users cannot change their login
> > name).
> >
> > If the new uid is part of the user profile, it must be accessible (via
> > some api) to allow reliable tracking the activity of any user.  My  
> > point
> > is simply that iff the uid is present but not accessible (via an api -
> > as I understand it is not), then it doesn't provide a complete
> > solution.
> >
> > On the other hand, if the new uid is indeed programmatically  
> > retrievable
> > (without having to write a custom method), then the problem is
> > (presumably) solved.
> >
> >
> > On Tue, 2008-06-10 at 08:51 -0700, Andrew Jaquith wrote:
> >
> >> Terry -- the uid is part of the user profile, and it is stored in the
> >> database. That is the "means" for tracking a unique user. Because  
> >> that
> >> work is complete, I closed the issue.
> >>
> >> Do you have specific suggestions on how to "track"?
> >>
> >> On Jun 10, 2008, at 7:15 AM, Terry Steichen <[EMAIL PROTECTED]>  
> >> wrote:
> >>
> >>> Well, then, until we include a means to actually use this unique id,
> >>> the
> >>> problem isn't really fixed, is it?
> >>>
> >>> On Tue, 2008-06-10 at 06:56 -0700, Andrew Jaquith wrote:
> >>>
> >>>> Let me be equally clear: yes, that's right.
> >>>>
> >>>> On Jun 10, 2008, at 3:02 AM, Terry Steichen <[EMAIL PROTECTED]>
> >>>> wrote:
> >>>>
> >>>>> Let me be clear - what you're saying is that a unique  
> >>>>> identifier has
> >>>>> been included in version 2.8 to uniquely distinguish a user,
> >>>>> regardless
> >>>>> of changes in name, but no specific method has yet been  
> >>>>> included to
> >>>>> use
> >>>>> it.  Is that correct?
> >>>>>
> >>>>> On Mon, 2008-06-09 at 23:23 -0700, Andrew Jaquith (JIRA) wrote:
> >>>>>
> >>>>>>    [ https://issues.apache.org/jira/browse/JSPWIKI-267? 
> >>>>>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> >>>>>> ]
> >>>>>>
> >>>>>> Andrew Jaquith closed JSPWIKI-267.
> >>>>>> ----------------------------------
> >>>>>>
> >>>>>>      Resolution: Fixed
> >>>>>>   Fix Version/s: 2.8
> >>>>>>
> >>>>>> I added the UID property to user profiles for this purpose in
> >>>>>> 2.7.0-
> >>>>>> svn-29. However, we are not using it strictly speaking for  
> >>>>>> tracking
> >>>>>> just yet. There are probably places in the code where we ought to
> >>>>>> print UserProfile.getUid() to the log file, but that's a future
> >>>>>> thing that we'll do as it makes sense.
> >>>>>>
> >>>>>> In the meantime, this bug is (strictly speaking) fixed.
> >>>>>>
> >>>>>>> No consistent means for maintaining a user's unique identity
> >>>>>>> ------------------------------------------------------------
> >>>>>>>
> >>>>>>>               Key: JSPWIKI-267
> >>>>>>>               URL: https://issues.apache.org/jira/browse/
> >>>>>>> JSPWIKI-267
> >>>>>>>           Project: JSPWiki
> >>>>>>>        Issue Type: Bug
> >>>>>>>        Components: Authentication&Authorization
> >>>>>>>  Affects Versions: 2.6.2
> >>>>>>>       Environment: All
> >>>>>>>          Reporter: Terry Steichen
> >>>>>>>          Assignee: Andrew Jaquith
> >>>>>>>           Fix For: 2.8
> >>>>>>>
> >>>>>>>
> >>>>>>> Now that we've modified JSPWiki to allow users to change not  
> >>>>>>> only
> >>>>>>> their Name but also their login name, I don't see any way for
> >>>>>>> JSPWiki administrator to keep track of users over time.  For  
> >>>>>>> many
> >>>>>>> reasons of administration, billing, user behavior management, I
> >>>>>>> think there should be some way to unambiguously identify a
> >>>>>>> particular user, no matter how often they may change their
> >>>>>>> profile.
> >>>>>>

Reply via email to