If object is missing authz info we vomit a messy error #14
Description
In a particularly messed up situation we saw:
o.groups['users'].group_raw
RestClient::ResourceNotFound: 404 Resource Not Found: <TITLE>404 Not Found</TITLE>
Not Found
The requested document was not found on this server.mochiweb+webmachine web server
fixie:0 > g=o.groups['users']
<Fixie::Sql::Group:0x00000002c6cdf0 @DaTa=#< @values={:id=>"8e3dd898084bae75c014a7056648d32d", :org_id=>"", :authz_id=>"15eee325aaf8c796ff1ec4529e5e21e6", :name=>"users", :last_updated_by=>"", :created_at=>2014-04-29 23:58:26 UTC, :updated_at=>2015-03-04 22:50:33 UTC}>>
fixie:0 > g.authz_api.get("groups/15eee325aaf8c796ff1ec4529e5e21e6")
RestClient::ResourceNotFound: 404 Resource Not Found: <TITLE>404 Not Found</TITLE>
Not Found
The requested document was not found on this server.mochiweb+webmachine web server
from /opt/rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/rest-client-1.6.8/lib/restclient/abstract_response.rb:48:in `return!'
The authz_id for the users group doesn't exist, and we hit authz and get a 403, which throws a big messy stacktrace. We should trap this and throw an exception that explains what's really happening.