Hi everyone.
I'm looking to use XWiki for our corporate intranet. I would like to authenticate users from our existing database, like it says on this page: http://www.xwiki.org/xwiki/bin/view/AdminGuide/Pluggable+Authentication
It says "Users can be authenticated against custom tables."
Can somebody tell me how to do this? Or do I need to write some custom code?
Thanks.
Sorry if the answer is documented somewhere; I haven't been able to find it.
--
Tim K
I know this has already been covered in earlier discussion but I can't
seem to get round the "An error occured during the registration process
(-1)." for new users.
I have read through the postings and the documentation but have had no joy.
Is it because we are on the wiki farm? We are at http://ukeig.xwiki.com/
Karen
--
Karen Blakeman, UKeiG Management Committee
88 Star Road, Caversham, Berks RG4 5BE, UK
Tel: 0118 947 2256 Int. +44 118 947 2256
Mobile: 07764 936733 Int. +44 7764 936733
Fax: 020 8020 0253 Int. +44 20 8020 0253
Mailto:Karen.Blakeman@rba.co.uk
http://www.rba.co.uk/
If you install xwiki with the supplied postgresql data the user list that
is installed is different from that assumed by the install instructions. It
would be really useful if this could be fixed.
In particular the list of users is:-
XWiki.FabriceMorisseau
XWiki.LudovicDubost
XWiki.MyTestUser
XWiki.MyTestUser3
XWiki.MyTestUser4
XWiki.MyTestUser5
XWiki.MyTestUser6
XWiki.TestUser
The install instructions assume that there is a user called Admin with a
password of admin, but this logon does not work.
Would it be possible to post a new version of the postgresql data on the
website so that users of this DB can follow the supplied instructions?
David
Am I correct to believe that when an XWiki document is deleted, its
history and all memory of its existence goes with it?
That would represent a hole in the auditability/recoverability features;
while it can be limited to appropriate people via the rights system, it
still leaves mysteries requiring access to server logs, at minimum, to
resolve.
brain[sic]
Anyone got pointers to help with installing either tinyMCE or the new XWiki implementation on a 0.9.840 XWiki instance? I don't seem to have got the trick of doing it right.
brain[sic]
Hi folks,
Currently trying to setup email sending for our xwiki server, and
following the outline provided at
(http://www.xwiki.org/xwiki/bin/view/Demo/SendMail3); but does not seem
to be functioning correctly for me. On my end, the xwiki server just
goes into an endless loop (like as though it's trying to access a large
chunk of data).
Has anyone set this up on their own local wiki server, and if so are
there any guideline configurations?
As XWiki becomes more popular, hopefully a wide variety of scripts
will become available and easy to install thanks to the new packaging
system. I'm wondering if we need to do anything to ensure scripts
coexist peacefully.
For example, I'm considering installing the Tagging script, but I'm
concerned that its use of window.onload and maybe functions it defines
will clash with other javascript code on the site.
Also, should there be a specific Javascript library that we expect
XWiki scripts to use, so that a page doesn't have to load up several
toolkits just so that different scripts can call their Ajax functions?
Furthermore, AFAIK it's not possible to define namespaces in Velocity.
I assume it's possible several scripts will try to use the same
variable names within the same page, resulting in confusion. Not sure
what workarounds there are for this.
Any thoughts? Am I just being paranoid? How do systems like Google ig
allow many custom widgets on the same page without clashes?
Regards,
Robin.
Another feature for editing which is sorely missed even by users of
non-WYSIWYG editors is the ability to search the text of a textarea.
When an XWiki document gets long, it's really painful when testing out
subtle changes or scripting which requires me to keep previewing while
editing, and going back to the edit screen which has now reset the field
to the top.
At the least, the ability to put line numbering in would be useful. I'm
planning to put up a bookmarklet to do that, except that it may
interfere with any onchange-triggerred scripting.
brain[sic]