-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorporate Commonalities WG recommendations on Simplification of Device object #64
Conversation
- Add recommended text on "Identifying a device from the access token" - Add 422 error response option - Explicitly define request body as optional
- Fix trailing space
- Rewrite section on handing of device identifiers to clarify that "device" in this context means "mobile subscription identifier", and not the mobile device (UE) itself
- Fix indentation
- Update phoneNumber schema as per current definition in Commonalities
|
||
### Validation mechanism: | ||
|
||
- The server will extract the mobile subscription identifier (i.e. MSISDN) from the access token, if available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason why it has to MSISDN? Should it be (e.g. MSISDN)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, this is internal implementation that no-one will ever audit, but it will almost certainly be MSISDN or equivalent (such as GPSI). However, I'm happy to change this to "e.g.".
Co-authored-by: Ramesh Shanmugasundaram - Spry Fox Networks <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Purely editorial and an improvement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍🏼
- Update Authorisation and Authentication section following update by Identity & Consent Management - Revise "Validation Mechanism" section to make it more implementation agnostic - Add additional error message codes
- Fix linting errors
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #61
Special notes for reviewers:
Request bodies were already optional
Changelog input
Additional documentation
None