[Ozone Ranger Plugin] Security Zones are not getting enforced during Authorization

Observed that Security Zones for Ozone Plugin are not getting enforced, and Ranger is relying on Non-Zone Policies for deciding the Access.

Steps:

1. Created a security zone finance-zone-20200728123343 
2. There is no policy granting access to volume-finance in service finance-20200728123343 which is attached to the security zone created in the 1st step.
3. Create ozone volume volume-finance as a hrt_21  test user. [hrt_21 is part of both users and finance groups]

Expected Result: Volume creation should be denied as there is no policy granting access in Zone attached service.

Actual Result: Volume creation is successful using a Non-Zone policy present [which provides access to hrt_21 test user]

 
Similar results are observed with multi-level resources [volume-bucket-key] in the zone, where the zone policy is not honored instead it relies on the Non-zone policy for deciding the access.

Any inputs on how to debug this further?