I don't know if this is your problem, but there is an error in the rest api documentation concerning for example the way to get of a policy thanks to the service-name and policy-name.
The error is a missing level in the api arborescence. In the documentation, you can see this : /public/v2/api/<service-name> And the correct path is in fact : /public/v2/api/service/<service-name> Hope it helps. Best regards. Lune Le 19 juil. 2016 23:22, "Don Bosco Durai" <bo...@apache.org> a écrit : > Aaron, are you still having this issues? Your previous mail said that you > found errors in the log file. > > > > Thanks > > > > Bosco > > > > > > *From: *"Stromas, Aaron" <aaron.stro...@rsa.com> > *Reply-To: *<user@ranger.incubator.apache.org> > *Date: *Tuesday, July 19, 2016 at 1:17 PM > *To: *"user@ranger.incubator.apache.org" <user@ranger.incubator.apache.org > > > *Subject: *Question about Ranger REST URL with service-name component > > > > Greetings, > > > > None of the REST API calls using the service-name do not work for me. All > of the following return HTTP 404 > > > > curl -iv -u admin:admin -X GET > http://192.168.26.111:6080/service/public/v2/api/servicedef/hdfs > > > > curl -iv -u admin:admin -H "Content-Type: application/json" -d > @hdfs-update-policy-by-name.payload -X PUT > http://192.168.26.111:6080/service/public/v2/api/Sandbox_hdfs/policy/appaccess > > > > curl -iv -u admin:admin -X DELETE > http://192.168.26.111:6080/service/public/v2/api/Sandbox_hdfs/policy/appaccess > > > > curl -iv -u admin:admin -X GET > http://192.168.26.111:6080/service/public/v2/api/Sandbox_hdfs/policy > > > > Service name Sandbox_hdfs and policy app access exist and the calls that > use ID rather than name work, so are the URLs incorrect? What should they > be? > > Thanks. > > > > Best regards, > > > > -Aaron > > > > — > > *Aaron Stromas | * RSA The Security Division of EMC | Practice > Consultant | Identity & Fraud Protection Practice | M +1 240 271 64 58 | >
