[RANGER-4188] updatePolicy results in 400 status code

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0, 2.4.0
• Fix Version/s: 3.0.0, 2.4.0
• Component/s: Ranger
• Assignee: Pradeep Agrawal
• Reporter: Pradeep Agrawal
• Created: 14/Apr/23 13:45
• Updated: 05/May/23 06:47
• Resolved: 05/May/23 06:47

Description

 

 

2023-04-12 16:05:31,526 INFO  org.apache.zookeeper.ClientCnxn: [Thread-2-SendThread(pfelker-dest-1.pfelker-dest.root.hwx.site:2181)]: Socket connection established, initiating se2023-04-12 16:30:53,674 INFO  org.apache.ranger.common.RESTErrorUtil: [https-jsse-nio-6182-exec-3]: Request failed. loginId=ranger, logMessage=policyID mismatch
javax.ws.rs.WebApplicationException: null
        at org.apache.ranger.common.RESTErrorUtil.createRESTException(RESTErrorUtil.java:338) [classes/:?]
        at org.apache.ranger.rest.ServiceREST.updatePolicy(ServiceREST.java:1782) [classes/:?]
        at org.apache.ranger.rest.ServiceREST.applyPolicy(ServiceREST.java:1749) [classes/:?]
        at org.apache.ranger.rest.ServiceREST.createPolicy(ServiceREST.java:1658) [classes/:?]

 

Issue Links

• is a clone of: RANGER-4112 Update servicedef by name results in 400 status code while the same request works with update servicedef using id
• is caused by: RANGER-3883 emailchange and passwordchange User REST API's work even when invalid user id is used in the url
• links to: Apache review request