Ok to set a variable to login, but maybe not in the config but in the=20
database, so admin can change it.
Also we can think to leave administrator always local, so if for example an=
=20
ldap server is down administrator can always login.
For the external services consider that xml-rpm authentication is already=20
working (look at wblogger class)...
Romeo
At 08.49 25/07/03 +0200, you wrote:
>Ok let's start developement debate.
>I'd like to work on the auth part of the product.
>Now it makes auth only towards the DB.
>I'd like to create a variable to set in the config (and then in the install
>proc) that gives to the user different options.
>The 3 that I' thinking right now are DB (as before), external service (such
>as a web services or other auth system that will be the master system) and
>LDAP.
>Obviously as written by Romeo there are others, but using this pattern
>we'll be able to add (plug-in) other auth method if needed.
>I've not a clear idea of how, but Id like to follow the ADODB pattern,
>defining some standard API that each system implement as it deems right.
>Since I'm not so experienced with envo my first doubt is does the code uses
>the user table in other points beside the auth and registration (since
>there are not the foreign key, a thing of whitch I sometimes feel the need,
>there should be less problems).
>
>Does anyone has some idea, advise ...?
>Luca
>N=ACHS^=B5=E9=9A=8A[)=A2{(=AD=E7[=C8Z=DEz=9A=DEn=E8=A5=B4=8F4D=EC=8A=D7=AC=
=8Aw%=B9=D8=A7=806=ADi=A9=A2=BBl=CA&=99=EA=DCx=FA+=B5=A9ljwE=A2=BB=A6=B1=AA=
=DEj=F6=A2=95=A6=E5zz0=8C'=AD=86=9D=B6=87Z=C9=A9=DDz{^=AE=DA0=8Av=A7\=97=A2=
=B5b=B2=E6=A5J=DB=9D=8A=83DNm=A7=FF=DA=B2=99=DE=B5=C9brK=AB=95=CA&=FE=20
>?=A6=C6=B4=D3]4=D3M=DA=BD=EF=DD=8A=B7=9C=B5=ABZ=B2=99=DE=B7N=F6=DFM=F4=D7=
=FD5{=E8=AD=EBb=A2w^=BD=E9fj)b=9E=20
>b=B2=D1'=BE=89n=B6*'u=EB=DE=ADX=AC=B6=CB(=BA=B7~=8A=E0zw=AD=86=DBi=B3=FF=E5=
=8A=CBl=B2=8B=ABq=E7=E8=AE=A7z=DF=E5=8A=CBl=FEX=AC=B6)=DF=A3=F7=A7=BE=89n=B6=
*'u=EB=DE
|
