search

camaraproject / DeviceLocation

Repository to describe, develop, document and test the DeviceLocation API family
Apache License 2.0
20 stars 33 forks source link

Are we happy with security scope for geofencing? #173

Closed bigludo7 closed 1 month ago

bigludo7 commented 4 months ago

Problem description As of today, in Geofencing API we have:

      security:
        - openId:
            - geofencing:subscriptions:write

Do this name look good? For me the fact that we 'write' a subscription is not the most relevant information but we need to more precise like geofencing:subscriptions:read-location

Possible evolution Change name to geofencing:subscriptions:read-location

Alternative solution

Additional context Discussion in progress here: https://github.com/camaraproject/Commonalities/issues/163

jlurien commented 4 months ago

We will join the discussion in commonalities

bigludo7 commented 1 month ago

We can close this one as it is solved here: https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#102-security-implementation - part b)