hi again
very sorry to disturbing you once again
i saw that i can get request from wikicontext
so in my own auth class i can get my user
no longer need a servlet to send user to the login form
great everything is fine BUT
first: i still have "you are not allowed to view this document ...." when the user log in
second : i can't log out
problem look like xwiki don't know my user
(in my AuthImpl i did all that it's found in LDAPAuthImpl...)
sorry again
(BTW if it's not the right place to ask this kind of questions, tell me, no problem...)
----Message d'origine----
>Date: Sat, 10 Nov 2007 23:19:23 +0100 (CET)
>De: "Jerome Velociter" <jerome(a)xwiki.com>
>A: "XWiki Developers" <devs(a)xwiki.org>
>Copie à : devs(a)xwiki.org
>Sujet: Re: [xwiki-devs] ntlm with xwiki
>
>Hello,
>>
>> First of all Sorry for creating a new topic
>>
>> thanks for your anwser Jerome.
>>
>> but Actually i have seen this feature
>>
>> i added jcifs and it works well
>> an other hand i have tested impletentetion for ldap its works too
>>
>> but i want a transparent authentication
>> so now the problem is :
>>
>> i would like to not have form login
>> i saw in code that we can define our login page with this property in
>> xwiki.cfg :
>> xwiki.authentication.loginpage (if null default is
>> /bin/login/XWiki/XWikiLogin)
>>
>> i've changed this property but no changes when template call
>>
>> $xwiki.getURL("XWiki.XWikiLogin", "login", "xredirect=$logredir"))
>>
>> i still got the same url : bin/login/XWiki/XWikiLogin?
>
>Actually, it's the expected behavior : the call asks for the URL of the
>XWiki.XWikiLogin document, under the login action and with a xredirect
>query string parameter. If you changed your authentication login page to
>XWiki.MyCustomLogin in the conf, the calls to login URL should ask for
>that document IMO. Also, you may have to modidy a bit the skin if you want
>the users to be redirected to the proper login page any case. If you are
>using albatross skin, you can look over global.vm and login.vm, there is
>also the header.vm file in the webapp/templates folder that calls for the
>login URL.
>
>Hope it's clear enough, as I'm not sure what you exactly want to do (In
>particuliar, I don't understand why you wany to post username to
>loginsubmit action, since you use third-party authentication).
>
>Tell us how it goes.
>
>Regards,
>Jerome.
>
>>
>>
>> the purpose of that is log-in link goes to my servlet , then i do ntlm
>> authentication (it already works), then i post user name to
>> /xwiki/bin/loginsubmit/XWiki/XWikiLogin
>>
>> in the same time i do my own version of authentification (get user info
>> (name mail,etc...) from another ldap without test of password cos already
>> done with ntlm)
>>
>>
>> So! how can i redirect log-in page ? thanks a lot
>>
>> ------------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi,
>>
>> You can implement your own version of the
>> com.xpn.xwiki.user.api.XWikiAuthService interface.
>>
>> There's already a LDAP impl existing (different from the XWiki default
>> one), so you can look over that too as an example.
>>
>> Then, you must precise in the xwiki.cfg configuration file that you want
>> to use your own class, with something like
>>
>> xwiki.authentication.authclass = com.mycompany.mypackage.MyXWikiAuthImpl
>>
>> Regards,
>> Jerome.
>>
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
Actually for each request i go through my implementation of AuthServiceImpl
(same that ldap without check password)
i though it was just called when i call loginsubmit action
the consequence is that my user is added to the default group each time
seems like it does not recognize the user so xwiki add it several time with the same name !!!
i go on...
Hi,
I am using for my diploma thesis xwiki and i want to authorize users
against shibboleth( http://shibboleth.internet2.edu/ )
I know that I must implements XWikiAuthService, but i don't know what the
methods do. So, there are three methods
public XWikiUser checkAuth(XWikiContext context) throws XWikiException;
public void showLogin(XWikiContext context) throws XWikiException;
public Principal authenticate(String username, String password,
XWikiContext context) throws XWikiException;
and which one is called when user come to xwiki? What is the difference
between checkAuth and authenticate method?
I want to implement lazy sessions, that means, when user click on login, he
will be redirected to shibboleth auth provider. The same case is when user
want to logout. Now i must to find out, if i need create user logins in
database or if it possible to create some session only login.
Thanks for reply
Jan Kodera
I am resending this because yesterday it didn't come through...
----------------------------------------------------------------------------------------------
Dear all,
I've been working on the refactoring of XEclipse and it is almost
ready for release.
There are several high and low level enhancements:
1) The UI has been partially rewritten by leveraging Eclipse framework
APIs.
Things now are a lot simpler at the code level. There are also some UI
restyling to make it nicer/more functional.
2) Offline support has been rewritten and now it works fine. It
seamlessly caches pages, and detects conflicts when there
have been remote modifications. The offline API is pretty simple and
well documented and should allow for future extensions hopefully
without too many problems (e.g., using an embedded XWiki as cache
storage).
4) An Eclipse RCP shell for building and using XEclipse as a
standalone application has been added.
There are still some minor things missing like commands for creating/
removing pages/spaces and some editor-synchronization logic. But this
is easy to implement and I'll do it tomorrow. Some documentation of
non-critical parts is also missing.
I would say that we can schedule a release on Monday.
In the meanwhile I invite you to build your own copy of XEclipse and
try it out.
In order to compile XEclipse do the following:
1) cd TEMP_DIR; svn co http://svn.xwiki.org/svnroot/xwiki/xwiki-extensions/xwiki-eclipse/trunk/
xeclipse
2) Download xeclipse-target-platform.tar.gz [1] from http://www.xwiki.org/fabio/xeclipse-target-platform.tar.gz
and unpack it in TEMP_DIR/xeclipse
3) Go to TEMP_DIR/xeclipse/plugins/org.xwiki.xeclipse.rcp and follow
the instructions in README.maven
At the end of the process you should obtain a .zip with XEclipse
compiled and packaged for your platform.
Unzip it wherever you want and launch the XEclipse binary.
Cheers,
Fabio
[1] This is of course a temporary location. Probably the target
platform will be moved to the maven repository and downloaded directly
from there by tweaking a bit the pom.xml
actually i want to post to submitlogin action to call my own authentification class wich is implements XWikiAuthServiceImpl
this class is a copy of ldap authentification class without check password
the purpose is to create a wiki user
but once user is logged a got a message "You are not allowed to view this document or perform this action"
(need to be automatically insert in a particular group)?
in log file : "Accept user even without account"
the other problem is that each time i do a request my user is replicated in
XWikiAllGroup (but this is cause of me ,though my code call each time authentification, don't know why yet)
i have another user that is known in xwiki
and i can't logged to xwiki anymore
i have a problem with
context.getWiki().saveDocument(doc, context.getMessageTool().get("core.comment.createdUser"), context);
does it check password through this methode??
actually i'm a little lost ...
----Message d'origine----
>Date: Sat, 10 Nov 2007 23:19:23 +0100 (CET)
>De: "Jerome Velociter" <jerome(a)xwiki.com>
>A: "XWiki Developers" <devs(a)xwiki.org>
>Copie à : devs(a)xwiki.org
>Sujet: Re: [xwiki-devs] ntlm with xwiki
>
>Hello,
>>
>> First of all Sorry for creating a new topic
>>
>> thanks for your anwser Jerome.
>>
>> but Actually i have seen this feature
>>
>> i added jcifs and it works well
>> an other hand i have tested impletentetion for ldap its works too
>>
>> but i want a transparent authentication
>> so now the problem is :
>>
>> i would like to not have form login
>> i saw in code that we can define our login page with this property in
>> xwiki.cfg :
>> xwiki.authentication.loginpage (if null default is
>> /bin/login/XWiki/XWikiLogin)
>>
>> i've changed this property but no changes when template call
>>
>> $xwiki.getURL("XWiki.XWikiLogin", "login", "xredirect=$logredir"))
>>
>> i still got the same url : bin/login/XWiki/XWikiLogin?
>
>Actually, it's the expected behavior : the call asks for the URL of the
>XWiki.XWikiLogin document, under the login action and with a xredirect
>query string parameter. If you changed your authentication login page to
>XWiki.MyCustomLogin in the conf, the calls to login URL should ask for
>that document IMO. Also, you may have to modidy a bit the skin if you want
>the users to be redirected to the proper login page any case. If you are
>using albatross skin, you can look over global.vm and login.vm, there is
>also the header.vm file in the webapp/templates folder that calls for the
>login URL.
>
>Hope it's clear enough, as I'm not sure what you exactly want to do (In
>particuliar, I don't understand why you wany to post username to
>loginsubmit action, since you use third-party authentication).
>
>Tell us how it goes.
>
>Regards,
>Jerome.
>
>>
>>
>> the purpose of that is log-in link goes to my servlet , then i do ntlm
>> authentication (it already works), then i post user name to
>> /xwiki/bin/loginsubmit/XWiki/XWikiLogin
>>
>> in the same time i do my own version of authentification (get user info
>> (name mail,etc...) from another ldap without test of password cos already
>> done with ntlm)
>>
>>
>> So! how can i redirect log-in page ? thanks a lot
>>
>> ------------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi,
>>
>> You can implement your own version of the
>> com.xpn.xwiki.user.api.XWikiAuthService interface.
>>
>> There's already a LDAP impl existing (different from the XWiki default
>> one), so you can look over that too as an example.
>>
>> Then, you must precise in the xwiki.cfg configuration file that you want
>> to use your own class, with something like
>>
>> xwiki.authentication.authclass = com.mycompany.mypackage.MyXWikiAuthImpl
>>
>> Regards,
>> Jerome.
>>
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.1.2.
This is a bug fix release following the release of XWiki Platform
1.1.2. This release also introduce experimental new rights management
system (not active by default).
Bugs fixed in 1.1.2:
* Impossible to translate page in 1.1.1.
* Error while importing a XAR containing XWiki.XWikiServerClass
object(s) in a non-virtual wiki.
* Issue in EditAction which allows to create a bad translation state.
* EditTranslations panel does not handle empty default language properly.
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise112
Thanks
-The XWiki dev team
Hi,
Since we've slipped a lot for the 1.2M2 release we need a new roadmap
again...
Right now the only thing holding up the 1.2M2 release is to commit the
new UI for rights mgmt on trunk (Thomas/Evelina should hopefully
finish this today and then I'll start the release).
So the plan is:
1.2M2: 12 Nov
1.2RC1: 26 Nov
1.2RC2: 3 Dec
1.2Final: promotion of 1.2RC2 as final on 8 Dec
Note 1: The goal is still to have a stable 1.2 by Javapolis 2007.
Note 2: This means that from now on, only bug fixes should be done for
the 1.2 release. If you need to commit stuff for 1.3 then let me know
and I'll branch 1.2.
Thanks
-Vincent
First of all Sorry for creating a new topic
thanks for your anwser Jerome.
but Actually i have seen this feature
i added jcifs and it works well
an other hand i have tested impletentetion for ldap its works too
but i want a transparent authentication
so now the problem is :
i would like to not have form login
i saw in code that we can define our login page with this property in xwiki.cfg :
xwiki.authentication.loginpage (if null default is /bin/login/XWiki/XWikiLogin)
i've changed this property but no changes when template call
$xwiki.getURL("XWiki.XWikiLogin", "login", "xredirect=$logredir"))
i still got the same url : bin/login/XWiki/XWikiLogin?
the purpose of that is log-in link goes to my servlet , then i do ntlm authentication (it already works), then i post user name to /xwiki/bin/loginsubmit/XWiki/XWikiLogin
in the same time i do my own version of authentification (get user info (name mail,etc...) from another ldap without test of password cos already done with ntlm)
So! how can i redirect log-in page ? thanks a lot
------------------------------------------------------------
Hi,
You can implement your own version of the
com.xpn.xwiki.user.api.XWikiAuthService interface.
There's already a LDAP impl existing (different from the XWiki default
one), so you can look over that too as an example.
Then, you must precise in the xwiki.cfg configuration file that you want
to use your own class, with something like
xwiki.authentication.authclass = com.mycompany.mypackage.MyXWikiAuthImpl
Regards,
Jerome.
Hi,
I'd like to modify the XWiki.getDocument(String fullname) API so that
it's possible to reference documents in other virtual wikis.
For example: getDocument("otherwiki:Space.Name")
This will add for example the ability to have Panels in one wiki and
use them in another wiki.
WDYT?
Thanks
-Vincent
Hi devs,
Just read an interesting post from John Casey (from Maven fame):
http://blogs.sonatype.com/john/2007/11/09/1194630418546.html
I haven't yet thought how we could apply this to XWiki but I think
this is definitely an idea we should explore. The really nice thing is
that it keeps the new code completely clean and moves all the
compatibility code in one clean location (that's the point of Aspects).
Dunno why I've never thought about this. Sounds such a nice use case
for Aspects.
-Vincent