12 May
2014
12 May
'14
2:38 a.m.
Why does this restriction exist? It makes it difficult to map through
to LDAP if we can't map to AD/LDAP username field that contain periods,
such as format of "firstname.lastname" which is quite common. Also, it
is possible to authenticate to xwiki using email address and password
rather than user id and password?
MT
12 May
12 May
3:22 a.m.
For legacy reasons. A long time ago, having dots in document names was
not really working, since a dot separates the document's space and name.
Plus the fact that users are just documents in the wiki.
This restriction is no longer relevant, except that there's a lot of
code that needs to be revisited to remove this restriction.
On 05/11/2014 08:38 PM, mctozzy(a)gmail.com wrote:
Why does this restriction exist? It makes it
difficult to map through
to LDAP if we can't map to AD/LDAP username field that contain periods,
such as format of "firstname.lastname" which is quite common. Also, it
is possible to authenticate to xwiki using email address and password
rather than user id and password?
--
Sergiu Dumitriu
http://purl.org/net/sergiu
3:30 a.m.
I thought that may have been the case...surely there can't be that many
places in the code where the user id text is validated? (And if there is
a period then can it not be held internally in escaped syntax?)
In any case, how do we address the consequential issues of this
constraint on things like ldap as per the rest of my msg?
On 12/05/2014 11:22 AM, Sergiu Dumitriu wrote:
For legacy reasons. A long time ago, having dots in
document names was
not really working, since a dot separates the document's space and name.
Plus the fact that users are just documents in the wiki.
This restriction is no longer relevant, except that there's a lot of
code that needs to be revisited to remove this restriction.
On 05/11/2014 08:38 PM, mctozzy(a)gmail.com wrote:
Why does this restriction exist? It makes it
difficult to map through
to LDAP if we can't map to AD/LDAP username field that contain periods,
such as format of "firstname.lastname" which is quite common. Also, it
is possible to authenticate to xwiki using email address and password
rather than user id and password?
9:46 a.m.
The LDAP authenticator remember the real LDAP uid in a special object
(1) stored in the user profile and use a "clean" (2) one for the XWiki
user id.
1:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
2:
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
On Mon, May 12, 2014 at 3:30 AM, <mctozzy(a)gmail.com> wrote:
I thought that may have been the case...surely there
can't be that many
places in the code where the user id text is validated? (And if there is a
period then can it not be held internally in escaped syntax?)
In any case, how do we address the consequential issues of this constraint
on things like ldap as per the rest of my msg?
On 12/05/2014 11:22 AM, Sergiu Dumitriu wrote:
--
Thomas Mortagne
For legacy reasons. A long time ago, having dots in document names was
not really working, since a dot separates the document's space and name.
Plus the fact that users are just documents in the wiki.
This restriction is no longer relevant, except that there's a lot of
code that needs to be revisited to remove this restriction.
On 05/11/2014 08:38 PM, mctozzy(a)gmail.com wrote:
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Why does this restriction exist? It makes it difficult to map through
to LDAP if we can't map to AD/LDAP username field that contain periods,
such as format of "firstname.lastname" which is quite common. Also, it
is possible to authenticate to xwiki using email address and password
rather than user id and password?
4005
days inactive
4005
days old
3 comments
3 participants
participants (3)
-
mctozzy＠gmail.com -
Sergiu Dumitriu -
Thomas Mortagne