No problem Rod, you're welcome/sorry for finding this bug! Kindest Regards
Chris Rogers Digital Developer [email protected] @portchris <https://twitter.com/SamJohnAllen> www.zeta.net 01202 237137 @ZetaAgency <https://twitter.com/ZetaAgency> On 11 November 2014 16:39, Rod Simpson <[email protected]> wrote: > It sounds like you guys have found a bug. Your write-ups of the problem > were great. I will ask the team to take a look. > > Thanks! > > > > -- > Rod Simpson > @rockerston <https://twitter.com/rockerston> > rodsimpson.com > > On November 11, 2014 at 9:38:04 AM, Chris Rogers ([email protected]) wrote: > > Hey Scott, > I am also having similar issues creating a connection between 2 > collections, specifically: users and devices. I have posted a question on > Stack Overflow here: > > http://stackoverflow.com/questions/26754807/apigee-admin-cannot-create-appropriate-user-permissions/26760633#26760633 > > An answer has been submitted but unfortunately hasn't resolved my issue, > but it could help yours. Let me know if you have found an appropriate > solution for your problem, as I am still trying to resolve this myself! > Many thanks > Chris > > > Kindest Regards > > Chris Rogers > Digital Developer > [email protected] > @portchris <https://twitter.com/SamJohnAllen> > > > > www.zeta.net > 01202 237137 > @ZetaAgency <https://twitter.com/ZetaAgency> > > On 11 November 2014 15:51, Scott Huey <[email protected]> wrote: > >> Hello, >> >> >> >> I just started experimenting with usergrid for possible use on a new >> project and have run into issues/questions with permissions I hoped someone >> could help with. >> >> >> >> It appears like wildcard permissions are not working like they are >> described in documentation with latest release (on my local machine and at >> the Apigee hosted instance) and I would like to confirm that what I am >> trying to do is correct and possible. >> >> >> >> In one particular scenario I would like to create entities that users can >> either "own" or "share" via connections. it would go something like this: >> >> >> >> create a new collection, let's just call it things and, in Default role >> give all users POST access to /things so anyone can add thing entities. >> >> >> >> When a user adds a new thing an "owns" connection would be created via >> the user: /user/[username|GUID]/owns/[NewThingGUID] >> >> In order to give full CRUD ops to the owning users a permission would >> already be established like this: GET,POST,PUT,DELETE: /users/${user}/owns >> >> It also seems like I should be able to do something like >> GET,POST,PUT,DELETE: **/owns >> >> >> >> When a user wants to share an entity he create a "shares" connection via >> the user: /user/[username|GUID]/shares/[ThingGUID] >> >> When I want to "share" an entity I would have already set up this >> permission on Default role for read only access GET: /users/${user}/shares >> or GET: **/shares >> >> >> >> Unfortunately neither of these works. The only thing so far I have gotten >> to work is: GET,POST,PUT,DELETE: /users/${user}/** >> >> which doesn't solve the problem because I am looking to set explicit >> permissions on different connection types and this only allows me to set >> one set of permissions globally on all. >> >> >> >> With this specific scenario I have actually tried several combinations of >> wildcard paths for permissions with no luck. >> >> >> >> I appreciate any input you could give into understanding why this isn't >> working and other possible solutions to accomplish the same scenario. >> >> >> >> Thank You for your time. >> >> >> >> Regards, >> >> Scott >> >> >> >> >> > >
ii_hv3lc7mj10_145efd805c737aec
Description: Binary data
