Originally submitted by pabloge (Pablo Guijarro) on 2020-08-25
In section 2.2 POST-based flow, it reads:
(A) In contrast to the web-based flow, the RP typically provides data (MNC/MCC,IMSI, or MSISDN) to determine the user's MNO to the discovery process. The service tries to determine the MNO based on this data. If this data is not present, the discovery service attempts to determine the MNO based on the RP's IP address. If that fails, the discovery process fails.
However, in section 3.2.1. (Issuer) Request, the “data not present” scenario does not seem to be allowed, because it states:
Either code, mcc, imsi, or msisdn must be present in the request.
I guess the latter should be modified to consider the option not to include any data, hoping for MNO resolution based on IP address to be possible.
Bitbucket status: new
Bitbucket origin: issue 192
In section 2.2 POST-based flow, it reads:
(A) In contrast to the web-based flow, the RP typically provides data (MNC/MCC,IMSI, or MSISDN) to determine the user's MNO to the discovery process. The service tries to determine the MNO based on this data. If this data is not present, the discovery service attempts to determine the MNO based on the RP's IP address. If that fails, the discovery process fails.
However, in section 3.2.1. (Issuer) Request, the “data not present” scenario does not seem to be allowed, because it states:
Either code, mcc, imsi, or msisdn must be present in the request.
I guess the latter should be modified to consider the option not to include any data, hoping for MNO resolution based on IP address to be possible.
Bitbucket status: new
Bitbucket origin: issue 192