DRAFT
...
Attendees & Representation
...
- #101 List endpoint for active sessions of authenticated user
- At least two different use cases
- As described originally within the issue: API consumer wants to get a list of open sessions across different subscribers
- within result would be only session created by the API consumer itself
- Herbert: in this case the API consumer will not get additional (personal) information from this endpoint which they haven't received already earlier (during session creation). Potentially possible with 2-legged token?
- Use case added by Jose: API consumer wants to get a list of sessions which are (potentially) already opened for a specific device
- Would require a 3-legged token and potentially consent from end-user?
- As described originally within the issue: API consumer wants to get a list of open sessions across different subscribers
- Discussion to be continued within the issue
- At least two different use cases
- #166 Extend QoS Profile queries to list profiles based on specific users or devices
- Discussion updated by Emil and Jose
- #265 to be done first (split of APIs)
- More clarifications on subscription will be added by Emil
- Description of parameters/filters within the issue needed
- #194 Add Application Function Id (afId) or Sponsor Id
- Syed opened the issue under identity and consent management project camaraproject/IdentityAndConsentManagement#126
- #238 Updating the project scope in the ReadMe
- PR will be reopened after MWC (see previous minutes)
- #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- #265 to be done first (split of APIs)
- #245 Update and enhance test definition file for QOD API
- Work in Device Location ongoing. Probably next week some issue will be opened in Commonalities (and TSC about GSMA Certification)
- #249 Duration in QosProfile and SessionInfo
- See previous minutes.
- #265 to be done first
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- PR will be created by Jose.
- #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
- Jose will prepare a PR next week, just the split without any further changes (incl. copying schemas, decision about common file later)
...