140 reputation
217
bio website stackoverflow.com
location Canada
age 24
visits member for 1 year, 9 months
seen yesterday

1d
revised Issues with module signing and SSIS catalog internal procedures
added 97 characters in body
1d
accepted Issues with module signing and SSIS catalog internal procedures
1d
comment Issues with module signing and SSIS catalog internal procedures
It already had connect, I think. Anyway, I granted that, still no dice. It seems as though the impersonation/certificate is just being ignored....If I add the restricted account to the ssisdb databases then it gives me errors about the permissions on the individual procs.
1d
comment Issues with module signing and SSIS catalog internal procedures
Thanks for all your help. I granted the appropriate permissions, but I'm still getting the following error:Msg 916, Level 14, State 1, Procedure get_user_info, Line 2 The server principal "RestrictedAccount" is not able to access the database "SSISDB" under the current security context.
1d
comment Issues with module signing and SSIS catalog internal procedures
I tried what you recommended (removing the execute as), yet the impersonation doesn't do anything (I get errors related to the permissions on my restricted account). I'm going to try the SQLCLR option now.
2d
awarded  Notable Question
Oct
22
comment Issues with module signing and SSIS catalog internal procedures
I've checked the owner (it's SA). I'm not sure I understand the revert message: the proc is in MSDB, and the user executing connects to the MSDB databases. I'm not explicitly calling REVERT anywhere. Is the problem with calling the procedures in the SSISDB databases from inside the proc?
Oct
21
comment Issues with module signing and SSIS catalog internal procedures
Thanks for adding the new info. I've verified none of the things are the issue (Except for #1 I am trying to impersonate a service account - not sure if that still applies). I've added more detail to the question.
Oct
21
revised Issues with module signing and SSIS catalog internal procedures
added 1306 characters in body; edited title
Oct
17
comment Issues with module signing and SSIS catalog internal procedures
I have signed the proc in MSDB as well.I receive the same error message when I call the procedure.
Oct
17
comment Issues with module signing and SSIS catalog internal procedures
@RLF No, my procedure lives in the msdb database. I'm calling the internal SSIS Catalog procedures to run the package.
Oct
17
asked Issues with module signing and SSIS catalog internal procedures
Oct
9
accepted Execute permission denied on object sp_start_job
Oct
7
comment Execute permission denied on object sp_start_job
@AaronBertrand Thanks, I may end up doing just that. As it is the database the procedure is in pretty much just has that procedure and nothing else, so it's pointless..
Oct
7
comment Execute permission denied on object sp_start_job
@AaronBertrand I don't particularly want to give the end user access to msdb. What other exposure am I giving by making the database trustworthy?
Oct
7
comment Execute permission denied on object sp_start_job
making the database trustworthy did the trick. Thanks a bunch!
Oct
7
asked Execute permission denied on object sp_start_job
Oct
1
awarded  Notable Question
Sep
15
accepted How can I restore ##MS_SSISServerCleanupJobLogin##?
Sep
4
awarded  Popular Question