Resources with periods cause issues when using mongodb as backend

[GregTurner]

If you use resource with periods, e.g., /path/myfile.ext, and mongodb, the periods are not encoded before being inserted into the DB. The result is the 'resources' collection that contains document with the resources names spilt on the period. E.g., "/path/myfile"/ext=True. This is causing a problem when trying to remove a resource because I assume the resource can't be found.

Workaround, encode periods with Unicode equivalent "\uff0E" in every caller to ACL api when using resources.

I recommend ACL encodes MongoDB control characters for the caller in mongodb-backend.js functions.

[timneedham]

Yeah, I'm hitting this one as well.
👍 The recommendation suggested by @GregTurner sounds ideal.

[manast]

we need a patch for this, but I am not able to provide it atm...

[hockeyhabit]

I'm getting a (similar) problem with periods in the userid field. When calling addUserRoles if the userid contains "[email protected]" the acl_meta collection gets: "bob@bob" : { "com" : true } and it should be "[email protected]": true

[prabhu]

I have fixed this issue here - colearnr@65abef8

Have submitted a PR including my other changes.

[manast]

Looks great. thanks.