ranger-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhay Kulkarni <akulka...@hortonworks.com>
Subject Re: Question about Ranger REST URL with service-name component
Date Wed, 20 Jul 2016 13:14:53 GMT
Hi Aaron,

I have marked the correct URLs below in red. Could you please use these URLs and share the
results? Also, it will help to open a documentation JIRA for these issues.

Thanks,
-Abhay

From: "Stromas, Aaron" <aaron.stromas@rsa.com<mailto:aaron.stromas@rsa.com>>
Reply-To: "user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>"
<user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>>
Date: Wednesday, July 20, 2016 at 6:16 PM
To: "user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>" <user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>>
Subject: Re: Question about Ranger REST URL with service-name component

Hi Bosco,

I still do. My previous post was concerning the create policy object where I had an error
in the JSON payload. I listed the requests that I still have problems with, namely,

  *   Get service definition by name
  *   Update policy by service-name and policy-name
  *   Delete policy by service-name and policy-name
  *   Search policies in a service

I forgot to mention that I'm testing in Hortonworks 2.4 sandbox.

Best regards,

-Aaron

-
Aaron Stromas  |  RSA  The Security Division of EMC | Practice Consultant  |  Identity &
Fraud Protection Practice |  M +1 240 271 64 58 |

From: Don Bosco Durai <bosco@apache.org<mailto:bosco@apache.org>>
Reply-To: "user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>"
<user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>>
Date: Tuesday, July 19, 2016 at 5:22 PM
To: "user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>" <user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>>
Subject: Re: Question about Ranger REST URL with service-name component

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.stromas@rsa.com<mailto:aaron.stromas@rsa.com>>
Reply-To: <user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>>
Date: Tuesday, July 19, 2016 at 1:17 PM
To: "user@ranger.incubator.apache.org<mailto:user@ranger.incubator.apache.org>" <user@ranger.incubator.apache.org<mailto: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  -X GET http://192.168.26.111:6080/service/public/v2/api/servicedef/name/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  -H "Content-Type: application/json" -d @hdfs-update-policy-by-name.payload
-X PUT http://192.168.26.111:6080/service/public/v2/api/service/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 DELETE  http://192.168.26.111:6080/service/public/v2/api/policy?servicename=Sandbox_hdfs&policyname=appaccess

curl -iv -u admin:admin -X GET http://192.168.26.111:6080/service/public/v2/api/Sandbox_hdfs/policy

curl -iv -u admin:admin -X GET http://192.168.26.111:6080/service/public/v2/api/service/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 |

Mime
View raw message