NTLM SSO removes Windows users on a PC, which is a member of a Windows
domain and who are logged into that domain, from the need to explicitly log
into eGW. They simply point IE to the eGW URL (eg. http://domain.com/egroupware/)
and start working. They can of cause explicitly log out and log in as an
other user.
For more information look at the README at
http://www.egroupware.org/viewvc/trunk/phpgwapi/ntml/README
2. different authentication for SyncML and/or GroupDAV
You can now use eg. an external auth provider for the login via the
WebGUI (eg. ADS) and the passwords stored in SQL for SyncML.
- retired the modifiy script as it's no longer necessary
- removed references and translations of the old scripts
- removed ldap version 3 switch from config
- create, edit & update the header
- install & update eGW
- config eGW
- create admin account
- install & update languages
- create & restore (install) backups
---> update, languages & backup can work for all domains at once
---> for use in 1.2 you have to update/switch the whole setup app to HEAD/trunk
- atm. all manageheader functionality is accessible
- reworked manageheader.php using the new setup_header class shared with setup-cli.php
=> install & update via cli is comming the next days
Works in 1.2 if you drop setup-cli.php and class.setup_header.inc.php in a 1.2 install.
+ setup_demo gives errors under postgres
+ setup_demo can save special chars in the admin name
- renamed setup_demo into admin_account, as setting up demo accounts is the least used function of it
- fixed warning db::delete missing params, if delete_all was checked
- added "working" explenation how to create a db, user und the necesary rights under postgres
- manageheader: renamed Domain --> Database instance (eGW Domain)
- manageheader: added further explenation of the host-field for Postgres and ODBC/MaxDB
- only needs host- and domain-name
- needs NO extra account on the ADS host
- can be used with accounts in SQL or LDAP to auto-create autheticated users
- new param to lowercase the user-names before auto-creating them (to deal with case-insensitve and case-sensitive system)
- the backup is independent of the used DB and can eg. be used to port an install to an other DB type
- autom. backup before upgrades of the DB structure
- installing backups instead an installation from scratch
- own backup screen in setup and admin to:
+ shedule repeating backups
+ up- and download of backups
+ creating and restoring backups
