Problem description
As described in recent merged PR177 in commonalities we have to update the security part, openId defined scope in geofencing-subscriptions yaml.
@bigludo7, if API is renamed to geofencing-subscriptions, should we have to rename as well events to org.camaraproject.geofencing-subscriptions.v0.area-...?
Problem description As described in recent merged PR177 in commonalities we have to update the
security
part,openId
defined scope in geofencing-subscriptions yaml.for GET we must have:
Expected behaviorhttps://github.com/camaraproject/Commonalities/pull/177
For GET & GET {id} we must have
for DELETE:
For POST
Alternative solution
Additional context @maxl2287 probably for you as you maintain this yaml ;)