Um... I wouldn't be that hasty, closing this one. I think it might
be pretty useful to be able to get extended properties from LDAP so
that we could generate the full names automatically. Or at least
survive login names nicely.
I mean, this is a pretty common issue.
/Janne
On 30 Oct 2007, at 10:17, Joerg Meyer (JIRA) wrote:
[ https://issues.apache.org/jira/browse/JSPWIKI-8?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Meyer resolved JSPWIKI-8.
-------------------------------
Resolution: Won't Fix
Use tools such as ldapvi, sed/awk and xsl to generate an export
from your ldap directory to userdatabase.xml in WEB-INF of jspwiki.
i.e. for a user "jmeyer"
<user loginName="jmeyer" wikiName="JoergMeyer" fullName="Joerg
Meyer" email="" password="" created="2007.10.29 at 09:36:23:643
JST" lastModified="2007.10.29 at 09:37:26:051 JST" />
This will solve most issues connected to the login.
As for the other issues
* spaces are handled correctly since 2.5
* the case issue mentioned (pages start with an upper case) is a
documented feature
Note:
I don't know of a way to request extended properties from ldap
through container authentication. So plain setups enabling ldap
container auth will probably deal with the same issues.
Links generated related to login name are incorrect (casing
incorrect)
---------------------------------------------------------------------
-
Key: JSPWIKI-8
URL: https://issues.apache.org/jira/browse/JSPWIKI-8
Project: JSPWiki
Issue Type: Bug
Components: Default template
Environment: linux/debian, tomcat5.5, jspwiki 2.4.73 and
jspwiki 2.5.139-beta, ldap/container authorization
Reporter: Joerg Meyer
Assignee: Andrew Jaquith
! Background
The tests were done using the brushed template on 2.4.73 and
standard on 2.5.139-beta.
Since most issues are similar, i believe, that the template does
not affect the issues. However brushed template and standard
template on 2.5.139-beta react differently to userFavorites.
If issues are known to exist only in the brushed template please
ignore the entries.
Our corporate template is at the moment a modified css for brushed
template (extra vanilla) for 2.4.73, however we are trying to
create a standalone template for standard 2.5.139-beta.
Note: On the results for favorites, the tests where done with
either jmeyerFavorites or JmeyerFavorites existing.
When i login using my ldap name: "jmeyer" i get the following
results:
! 2.4.73
* "G'day, jmeyer" points to page "Jmeyer" instead of "jmeyer"
* "This page (revision-11) was last changed on 22-Oct-07 11:18 AM,
+0900 by jmeyer" points to "Jmeyer" instead of "jmeyer"
* User in "RecentChanges" is correctly "jmeyer" and points to
"jmeyer"
* "jmeyerFavorites" is correctly included, the link "Favorites"
points correctly to the link "jmeyerFavorites"
* "JmeyerFavorites" does not get included, no "Favorites" box
* creating a page with first letter lowercase will automatically
"rename" it. I.e. "jmeyerFavorites" to "JmeyerFavorites" (this
makes it impossible to create favorites)
* if a page with first letter lowercase already exists, editing it
will not rename it
* renaming any page to first letter lowercase will automatically
generate a page with first letter uppercase
(this makes it impossible to rename any page to correct user pages
or favorites)
* It seems that the page "jmeyer" cannot be renamed
(this may be true for all pages starting with a lowercase letter)
* going to a page "jmeyer" when there is only a page "Jmeyer" will
resolve correctly
* going to a page "Jmeyer" when there is only a page "jmeyer" will
try to create the page "Jmeyer"
* weather a page can be found or not has no impact on the link
marking when the case does not match exactly
! 2.5.139-beta
* "G'day, jmeyer (authenticated)" points to page "Jmeyer" instead
of jmeyer
* "This page (revision-23) was last changed on 25/10 by jmeyer"
points to "Jmeyer" instead of "jmeyer"
* User in "RecentChanges" is correctly "jmeyer" and points to
"jmeyer"
* "jmeyerFavorites" is correctly included, however the link
"Favorites" points to "JmeyerFavorites" instead of "jmeyerFavorites"
* "JmeyerFavorites" does not get included, however "Favorites" box
gets created (shows this site does not exist on expanding), the
link "Favorites" points to "JmeyerFavorites"
* creating a page with first letter lowercase will automatically
"rename" it "jmeyerFavorites" to "JmeyerFavorites"
* if a page with first letter lowercase already exists, editing it
will not rename it
* It seems that the page "jmeyer" cannot be renamed
* going to a page "jmeyer" when there is only a page "Jmeyer" will
resolve correctly
* going to a page "Jmeyer" when there is only a page "jmeyer" will
try to create the page "Jmeyer"
* renaming any page to first letter lowercase will automatically
generate a page with first letter uppercase
* weather a page can be found or not has no impact on the link
marking when the case does not match exactly
! Result
Weather page names should start with an upper case letter or not
is irrelevant to the the discussion of correct user names.
If, as in our case, the login names are generally lowercase, then
none of the automatically created links except the RecentChanges
will be generated correctly. In most cases user pages cannot be
created at all.
Changing the login name to a different field in ldap (i.e. full
name) has other issues, as spaces in names may get resolved in
"G'day ..." however RecentChanges will never have links.
This is also not really a solution in our case, as all other
applications and portals throughout the company use the login name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
