Subject | problem with procedure's privileges not being applied |
---|---|
Author | unordained |
Post date | 2010-03-26T16:16:45Z |
I have the following situation:
user A is granted EXECUTE to procedure B
user A is granted SELECT, INSERT to table D
procedure B is granted SELECT, UPDATE to table D
D is a 'global temporary table'. The user inserts into D, then calls procedure B
to perform some updates on it, then goes back to retrieve the results.
As user A, when I try to execute procedure B, it tells me the user does not have
update/write privileges to table D. While that's true, it shouldn't be relevant,
as the procedure being called does have update privileges. That's how it's
supposed to work, right? I'm pretty sure it's working on all my other secured
procedures, just not this one.
This is with FB 2.1.1; is it possibly a corrupted-ACL issue? I haven't gone
anywhere near the limit indicated in CORE-216. Flamerobin tells me I've granted
those privileges as described above; I've tried disconnecting & bouncing the FB
server, that hasn't changed the behavior.
What should I try? Revoking & re-granting privileges? Dropping the procedure
entirely? Backup/restore?
Thanks,
-Philip
user A is granted EXECUTE to procedure B
user A is granted SELECT, INSERT to table D
procedure B is granted SELECT, UPDATE to table D
D is a 'global temporary table'. The user inserts into D, then calls procedure B
to perform some updates on it, then goes back to retrieve the results.
As user A, when I try to execute procedure B, it tells me the user does not have
update/write privileges to table D. While that's true, it shouldn't be relevant,
as the procedure being called does have update privileges. That's how it's
supposed to work, right? I'm pretty sure it's working on all my other secured
procedures, just not this one.
This is with FB 2.1.1; is it possibly a corrupted-ACL issue? I haven't gone
anywhere near the limit indicated in CORE-216. Flamerobin tells me I've granted
those privileges as described above; I've tried disconnecting & bouncing the FB
server, that hasn't changed the behavior.
What should I try? Revoking & re-granting privileges? Dropping the procedure
entirely? Backup/restore?
Thanks,
-Philip