Re: [Phpgroupware-users] FAQ? and admin authentication bugs

[Chris Weiss]

these are all good, but very hard to implemet in a true cross platform way.
htaccessing the setup section is a good thing, and can be done by any admin even
right now.  Can't really be the default because phpgw runs on way more just
apache/linux.

When the setup app was being created i suggested a combo shell script/web based
setup like what the Discus message board uses.  It was linear to say the least.

Patrick Price (address@hidden) wrote*:
>
>
>>
>>If you think there is a better way, suggest one.
>>
>
>How about:
>
>
>1: Scrap the authentication entirely for config/setup and put /setup
>pages in a .htaccess protected directory (or secure by obfuscation).
> Lots of packages do this.  So phpGroupWare wants to be different.
> That's cool, but if by different you mean being harder to setup, use
>and understand, then different is bad.
>
>OR
>
>2:  Generate a session id for config/setup login the same as for other
>phpGroupWare logins.  Use the same API the normal accounts use to login.
> The session id's seem to work well.
>
> Or roll the configuration pages into an app which is automatically
>installed as part of the admin account.   This means removing the
>so-called convenience of not having to hand-edit any configs prior to
>installation.  Set a couple of paths, run a script to create the admin
>and demo accounts, then login as admin and complete the configuration.
> One admin login instead of three (setup/config; header; admin) as it
>has now.
>
>
>-Patrick Price
>
>
>
>_______________________________________________
>Phpgroupware-users mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-users
>