Timeline for sa doesn't have permissions to other database through synonyms with the Service Broker

4 events

when toggle format	what		by	license	comment
Sep 26, 2017 at 1:50	comment	added	Solomon Rutzky		Kin, sorry, I wasn't implying that you neglected to mention it. I was just trying to emphasize the point since many people don't mind the risk if the alternative is too difficult or just won't work. And since the perception is that certificates / module signing is difficult / complex, a lot of people opt for just going with `TRUSTWORTHY ON`. So, I've been hoping that presenting it as an unnecessary risk, as opposed to merely "risky", will allow people to focus more on the better solution, or at least not automatically dismiss it without even taking a closer look.
Sep 26, 2017 at 1:39	comment	added	Kin Shah		Thats valid and is reflected in my answer `risky in terms of security approach`. I liked your linked answer +1 to that.
Sep 25, 2017 at 20:42	comment	added	Solomon Rutzky		`TRUSTWORTHY` is pretty much never needed as module signing handles nearly all scenarios (if not all), and isn't really that hard to set up. Thanks for the link to Remus's post (+1 for that alone) as that contained the one minor detail I was missing from getting it working. I now have a working example of this, in the "Ideal Solution (T-SQL)" section, in my answer to a similar question.
Nov 26, 2015 at 20:22	history	answered	Kin Shah	CC BY-SA 3.0