I updated all YAMLs with text on multi-SIM scenario handling, and also the "identifying the device from the token" text for the device roaming API.

I had a question on identifying the device for the subscription APIs. Currently device is a required parameter of the Subscription Request. So does this mean that subscriptions can only be created with a 2-legged token? Or should device actually be optional?

@camaraproject/device-status_maintainers
info.description now updated for all APIs, and ready for review

@bigludo7
My question in the comment above is still open. Is it correct that a device identifier is required to create a subscription? If so, what are the rules when a 3-legged token is used to create the subscription?

Hi @eric-murray

Is it correct that a device identifier is required to create a subscription?

At least yes for the subscriptions for device status or for geofencing.

If so, what are the rules when a 3-legged token is used to create the subscription?

We have specified in the design guideline that: "If 3-legged access token is used, the POST and GET responses must not provide any device identifier.". Which mean that, like for non subscription API, we did not accept an identifier in the subscription body when we find the identifier from the token.

in the event-subscription-template.yaml you find the 422 UNNECESSARY_IDENTIFIE error specified.

@bigludo7
But if an explicit device identifier is always required, does that not prevent a 3-legged token from being used to create a subscription (because that will trigger the 422 UNNECESSARY_IDENTIFIER error)?

In any case, I raised the issue explicitly in Issue #241. If it is correct that an explicit device identifier is always required, I'd like to understand the 3-legged token scenario for the documentation.

@bigludo7 @sachinvodafone Are you OK with this PR?

@bigludo7 @sachinvodafone Are you OK with this PR?

Hi @akoshunyadi - Yes - We can continue the discussion with @eric-murray in #241