is indicated. When this binding is created, as it is identified by a unique Id no other binding with the sane cofiguration can be created.
Therefore an Exception is required, as below commented
2) Improve description in deleteBlockchainPublicAddress
Rephrase this wording:
Note: Due to this, the API Server must validate that the id included in the request refers to a bind for a mobile phone number belonging to the user identified by its sub in the Access Token and, when identifier_bound_scopes are used, validate that the id included in the request refers to a bind for a mobile phone number appearing in the list of identifier_bound_scopes for the scope protecting this endpoint.
Possible evolution
1) Manage POST duplication of bindings - HTTP 409 - CONFLICT
2) Note: Due to this, the API Server must validate that the id included in the request refers to a bind for a mobile phone number belonging to the user identified by its sub in the Access Token.
Problem description
1) When creating a binding:
is indicated. When this binding is created, as it is identified by a unique Id no other binding with the sane cofiguration can be created. Therefore an Exception is required, as below commented
2) Improve description in deleteBlockchainPublicAddress
Rephrase this wording: Note: Due to this, the API Server must validate that the
idincluded in the request refers to a bind for a mobile phone number belonging to the user identified by itssubin the Access Token and, when identifier_bound_scopes are used, validate that theidincluded in the request refers to a bind for a mobile phone number appearing in the list of identifier_bound_scopes for the scope protecting this endpoint.Possible evolution 1) Manage POST duplication of bindings - HTTP 409 - CONFLICT
2) Note: Due to this, the API Server must validate that the
idincluded in the request refers to a bind for a mobile phone number belonging to the user identified by itssubin the Access Token.Alternative solution N/A
Additional context N/A