Re: [GENERAL] DB Authentication Design

2014-01-13 Thread François Beausoleil
Hello Chris, Le 2014-01-12 à 23:24, Chris Travers a écrit : > > On Sun, Jan 12, 2014 at 6:30 AM, François Beausoleil > wrote: > Hi all, > > I'm thinking that all apps that connect to the database should have their own > user. For example, the web application process is one user, then a report

Re: [GENERAL] DB Authentication Design

2014-01-12 Thread Chris Travers
On Sun, Jan 12, 2014 at 6:30 AM, François Beausoleil wrote: > Hi all, > > I'm thinking that all apps that connect to the database should have their > own user. For example, the web application process is one user, then a > report builder process should have another user, and a different process >

Re: [GENERAL] DB Authentication Design

2014-01-12 Thread Sameer Kumar
On 12 Jan 2014 22:31, "François Beausoleil" wrote: > > Hi all, > > I'm thinking that all apps that connect to the database should have their own user. For example, the web application process is one user, then a report builder process should have another user, and a different process that imports

Re: [GENERAL] DB Authentication Design

2014-01-12 Thread Szymon Guz
On 12 January 2014 15:30, François Beausoleil wrote: > Hi all, > > I'm thinking that all apps that connect to the database should have their > own user. For example, the web application process is one user, then a > report builder process should have another user, and a different process > that i