Re: [firebird-support] Re: Inssuficient rights for operation....
I find the error... It is not a FIREBIRD problem..it's BDE (Borland database engine) alias problem connection to database. When I install BDEINfoSetup, the INTRBASE alias have not the ROLE NAME attribute. From my application i provide to BDE alias username, password and role, but because ROLE NAME attribute not exist in BDE alias, the connection is made...without role...and the error appear!!! The solution: in key [HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\Settings\DRIVERS\INTRBASE\DB OPEN] append "ROLE NAME"="" and the application work fine!
Re: [firebird-support] Re: Inssuficient rights for operation....
> Hello. I used Firebird 1.5.6 on server on WIN7, a database with a role with > full rights, and a user defined in ROLE, USER. > I have a problem. In the network with a application, on different client > station, login with the USER, all functions work OK. > > From server or another WIN7 station, with USER login, a have one error, with > insufficient sql rights for operation, no permission to read/select acces to > TABLE. All different functions work OK. ROLE with GRANTS in all tables. > > The solution from win7 is to give rights on USER for table CONFIG_BALANTA, the > rights from the ROLE give this error > > > WHY THE DIFFERENT functionality? Same user, same rights on database. Is the user is providing the role name at connect time? -- With regards, Thomas Steinmaurer http://www.upscene.com Professional Tools and Services for Firebird FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
RE: [firebird-support] Re: Inssuficient rights for operation....
>Hello. I used Firebird 1.5.6 on server on WIN7, a database with a role with >full rights, and a user defined in ROLE, USER. >I have a problem. In the network with a application, on different client >station, login with the USER, all functions work OK. >From server or another WIN7 station, with USER login, a have one error, with >insufficient sql rights for operation, no permission to read/select acces to >TABLE. >All different functions work OK. ROLE with GRANTS in all tables. >The solution from win7 is to give rights on USER for table CONFIG_BALANTA, the >rights from the ROLE give this error >WHY THE DIFFERENT functionality? Same user, same rights on database. You may well know all I'm writing here, just thought I should point it out if it happened to be a simple misunderstanding. It does not matter from where you log in. What does matter, is username (obviously) and that you connect using the correct role. Let's say I'm a member of two separate roles: DB_READ and DB_WRITE which have the obvious rights to a table that I have no access to myself. If I connect to the database specifying DB_WRITE as the role, I can do whatever I want, if I use DB_READ when connecting, then I can read, but not write data and if I do not specify any role when connecting, then I cannot do anything (not even read) unless rights have been granted me as a user rather than any role I'm a member of. HTH, Set
