Hi all,
I wanted to take advantage of an ldap server for user authentication
but as others already encountered there was no support for SSL and I
needed it.
I attach a patch which add support for SSL connections to the ldap
server. To activate the SSL layer, I added a new configuration parameter
in xwiki.cfg (xwiki.authentication.ldap.ssl) which has to be set to 1.
Of course the ldap port has to be changed too (to 636).
In order for the SSL connection to be established, the CA certificate
which delivered the SSL certificate of the ldap server must be added to
the trust store of the JSSE extension.
>From the Sun JSSE documentation:
The search order for the locating the trust store is:
1) <java-home>/lib/security/jssecacerts, then
2) <java-home>/lib/security/cacerts
If the file jssecacerts exists, then cacerts is not consulted.
So in order to make it work you have to create a trust store named
jssecacerts with the following command and place it in the suitable
directory of the JRE or JDK used by your container:
keytool -import -trustcacerts -alias ca -file cacert.crt -keystore jssecacerts
(answer yes when asked if you want to trust the certificate)
I read on the web the default password for cacerts is 'changeit' so I
used that, I didn't try yet with another password for the trust store.
I believe if the SSL certificate of the ldap server is self signed you
need to import it instead of the CA but I did not try.
The patch makes use of com.sun.net.ssl.internal.ssl.Provider as the hard
coded security provided, it should maybe be put as a parameter for
people not running Sun JVMs.
I'm a newbie to xwiki so don't hesitate to critize the patch or give me
feedback.
Philippe
I am looking to use XWiki with Acegi SSO and CAS. Has anyone done this
and if not can anyone provide information and level of difficulty in
doing this?
Many Thanks,
Jean
Hi,
I'd like to define a location in SVN where we can put XWiki
applications (i.e. sets of xwiki pages). For example I'd like to put
the Selenium application I wrote in there. I've been thinking about
where best to put these and here's my proposal:
* Create a xwiki-applications directory (with trunk/, branches/ and
tags/) in svn.forge.objectweb.org/svnroot/xwiki
* Have the following directory structure:
xwiki-applications/trunk/
|_ wikis/
|_ default/
|_ applications/
|_ panels/
|_ selenium/
|_ blog/
|_ calendar/
|_ ...
* The default/ module will depend on several applications like
panels, blog, calendar, etc.
* All modules in xwiki-applications all produce a XAR when built
* We move the current xwiki/xwiki/trunk/wikis/** to xwiki-
applications/trunk/wikis/**
* There's already a xwiki-apps/ director y in SVN (for agilepm and
gelc). I'm proposing to rename it to xwiki-extensions/ and to move
agilepm to a sandbox. I'm proposing to create a sandbox for
applications in xwiki-applications/trunk/sandbox and move agilepm in
there.
Let me know if you're ok with this.
For jeremi and everyone workong on gelc, it shouldn't have much
impact apart from the fact that you'll need to copy any uncommitted
changes in the new directory (but that's a single copy - Simply make
sure you don't copy the .svn files and you should be good - I have
done that several times and it's very easy actually).
Note: The reason this is urgent is that I need to commit the selenium
application in order to start writing more functional tests and to
formalize how we do our functional tests. We need that ASAP for 1.0.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi,
Some user (Jerome Lacoste) has commented to me that XWiki URLs are a
bit too complex and should be simplified and cleaned as much as
possible. I agree with him.
Take for example: http://www.xwiki.org/xwiki/bin/view/Main/WebHome
Wouldn't it be nice is this was simplified to http://www.xwiki.org/
Main/WebHome?
This would mean view is the action by default.
I guess we could have: http://www.xwiki.org/Main/WebHome?action="view|
edit|..." with view being the default.
The /xwiki/ part will be able to be removed once we fix the jira
issue about removing the hardcoding about it.
That leaves the /bin/ path. I'm not sure why it's there and what it's
doing. I can see some hardcoded /testbin/ in the code but I thin this
is probably some leftover that we should remove (or do differently).
So what's the reason for /bin/?
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi,
I've created a XWIKI_1_0_BETA_4 branch for the b4 release.
Work can now start for beta 5 on the 1.0 branch.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
As Paul, I've stumbled upon this when using a tick (') in the
search box at xwiki.org.
It appears to be resolved on the dev version, but you really
should backport the fix to xwiki.org as it is a serious security
threat.
Pablo