Toni, > You have a username/password combination set for the application that > the application uses to request eg. authentication data from the > database. Alternatively, you leap and implement OpenID, which "solves" > all other problems for you.
This sort of a scheme works with application users stored in a table. However, LedgerSMB desires to use *database users* (i.e. ROLES) so that the same set of access restrictions can be maintained across 3rd-party applications which connect to the database. -- Josh Berkus PostgreSQL @ Sun San Francisco ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
