Re: [Phpwiki-talk] user authentication

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I vote for a carefull review of how the new authentication works (Reini=20
would need to help with some info) and then going and fixing the thing. =20
Just going at the source php files is too time consuming.  So, Reini,=20
would you write us a story, with some details on assumptions, classes=20
and methods (at least main ones)?

Reini put a lot of good work into this, I think, and it'd be good to=20
take this as a starting point and move ahead.  Although, I do expect a=20
few bigger fixes/solutions to have to be rewritten there.

Barrow H Kwan wrote:

>
> I think I have the same error like this and still can't figure out=20
> what is going wrong.
>
> I guess we have to look for different wiki implementation that support=20
> authentication.  like tikiwiki but they have more than what I need :(
>
>
>
>
> *<EAG...@RE...>*
> Sent by: php...@li...
>
> 06/15/2004 11:00 AM
>
> =09
> To
> 	<bh...@th...>, <ru...@x-...>
> cc
> 	<php...@li...>,=20
> <php...@li...>
> Subject
> 	RE: [Phpwiki-talk] user authentication
>
>
>
> =09
>
>
>
>
>
> Setting USE_DB_SESSION=3Dtrue I still have the same problem.
> =20
> Setting USE_DB_SESSION=3Dfalse  I have this error message:
> =20
> *Fatal error*: Cannot instantiate non-existent class: file_passwd in=20
> */usr/local/apache/htdocs/phpwiki-1.3.10/lib/WikiUserNew.php* on line=20
> *2122*
> Any idea ?
> -----Mensaje original-----*
> De:* php...@li...=20
> [mailto:php...@li...]*En nombre de *Barrow=20
> H Kwan*
> Enviado el:* martes, 15 de junio de 2004 12:17*
> Para:* Reini Urban <rurban*
> CC:* php...@li...;=20
> php...@li...*
> Asunto:* Re: [Phpwiki-talk] user authentication
>
>
> I have the same problem ( I have posted this few days ago on a=20
> different thread but got no answer ).  I use Postgresql to store pages=20
> and use file base authentication.   I did try to set USE_DB_SESSION to=20
> true ( try to set it to false as well ), but it didn't work ( in fact=20
> I got some error when I set it to false ).
>
> Does the authentication really work on phpwiki?  I didn't mean it is=20
> broken but not work as everyone thought.  ( I don't think login in=20
> each page is right ).
>
>
>
> *Reini Urban <ru...@x-...>*
> Sent by: php...@li...
>
> 06/15/2004 07:39 AM
>
> =09
> To
> =09
> cc
> 	php...@li...
> Subject
> 	Re: [Phpwiki-talk] user authentication
>
>
>
>
> =09
>
>
>
>
>
>
> EAG...@RE... schrieb:
> > I have the same problem using File authentication, (a file like=20
> /etc/shadow) ,
> > I need login in each page.
> > Is these solution right for my problem ?
>
> No, you are experienceing lost sessions.
> You can try to set USE_DB_SESSION true or false, until you find the rea=
l
> solution to your problem.
>
> > -----Mensaje original-----
> > De: php...@li...
> > [mailto:php...@li...]En nombre de Reini
> > Urban
> > Enviado el: martes, 15 de junio de 2004 4:00
> > Para: Lisa Glendenning
> > CC: php...@li...
> > Asunto: Re: [Phpwiki-talk] user authentication
> >
> > Lisa Glendenning schrieb:
> >>I am trying to use HttpAuth to authenticate through a Kerberos pop-up
> >>window.  This is working fine - except for anything requiring
> >>administrative privileges.  It is basically impossible to log on as t=
he
> >>administrator.  I have tried making the adminstrator an existing
> >>Kerberos user and a separate WikiWord.  I've also tried many
> >>combinations of the user authentication options.  No matter what, the
> >>adminstrative login won't 'stick'.  Every page asks for the admin log=
in,
> >>and actions done won't actually take effect (such as unlocking a page=
).
> >>It will default back to the Kerberos login.  Any thoughts?
> >
> >
> > You are right. This is an overthought with HttpAuth.
> > I would suggest to setup an Administrators group and add some user (n=
ot
> > ADMIN_USER) to this group. This user will have Admin Permissions then=
,
> > but not the special admin login method, which does not work for http
> > auth (yet).
> >
> > I usually create this page:
> > CategoryGroup
> >
> > * [Administrators]
> >
> > and this page:
> > Administrators
> >
> > * MyAdminUser
> >
> > ----
> > CategoryGroup
> --=20
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN=
D
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
> AVISO LEGAL:
> Esta informaci=F3n es privada y confidencial y est=E1 dirigida =FAnicam=
ente=20
> a su destinatario. Si usted no es el destinatario original de este=20
> mensaje y por este medio pudo acceder a dicha informaci=F3n por favor=20
> elimine el mensaje. La distribuci=F3n o copia de este mensaje est=E1=20
> estrictamente prohibida. Esta comunicaci=F3n es s=F3lo para prop=F3sito=
s de=20
> informaci=F3n y no debe ser considerada como propuesta, aceptaci=F3n ni=
=20
> como una declaraci=F3n de voluntad oficial de REPSOL YPF S.A. y/o=20
> subsidiarias y/o afiliadas. La transmisi=F3n de e-mails no garantiza qu=
e=20
> el correo electr=F3nico sea seguro o libre de error. Por consiguiente,=20
> no manifestamos que esta informaci=F3n sea completa o precisa. Toda=20
> informaci=F3n est=E1 sujeta a alterarse sin previo aviso.
>
> This information is private and confidential and intended for the=20
> recipient only. If you are not the intended recipient of this message=20
> you are hereby notified that any review, dissemination, distribution=20
> or copying of this message is strictly prohibited. This communication=20
> is for information purposes only and shall not be regarded neither as=20
> a proposal, acceptance nor as a statement of will or official=20
> statement from REPSOL YPF S.A. and/or subsidiaries and/or affiliates.=20
> Email transmission cannot be guaranteed to be secure or error-free.=20
> Therefore, we do not represent that this information is complete or=20
> accurate and it should not be relied upon as such. All information is=20
> subject to change without notice.
>