[ 
https://issues.apache.org/jira/browse/JSPWIKI-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621526#action_12621526
 ] 

Andrew Jaquith commented on JSPWIKI-268:
----------------------------------------

Terry -- thanks for the quick follow-up. I'll close this, but you should 
re-open it if you need to.

Regarding your question -- there are plenty of online systems that allow you to 
change your login ID. Just to name two off of the top of my head: Amazon, and 
Parallels Business Automation (which many hosting providers use).

Both of these, incidentally, require the e-mail address as the login ID. It 
wouldn't make sense for JSPWiki to have that  same requirement because of the 
huge number of integration scenarios we must support, very few of which 
recognize e-mail as the canonical identifier.

I know this isn't the answer you wanted. We probably *should* make the ability 
to change the login ID configurable. But it won't be in the 2.8.0 release. 
Maybe 2.8.1 or 3.0.


> Changing your name deactivates group membership until logout/login
> ------------------------------------------------------------------
>
>                 Key: JSPWIKI-268
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-268
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Authentication&Authorization
>    Affects Versions: 2.6.2
>         Environment: All
>            Reporter: Terry Steichen
>            Assignee: Andrew Jaquith
>            Priority: Minor
>             Fix For: 2.8
>
>
> If a user changes their name, when you check your group memberships again, 
> there are none.  If you logout and then login again, the group memberships 
> are restored.  (However, the membership is now based on the new name.)  This, 
> in and of itself, is a minor annoyance.  However, I believe it's related to 
> JSPWIKI-267- if this is resolved so that users can not change their login 
> name, then the logic that ends up changing the group membership name will 
> presumably be dropped and this issue will probably disappear.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to