API Access Requests to Indian MNO's

For API Access Requests made to Indian Operators, either you must be registered in the MC Link programme. Please see this website for more information.

Or, you need to be in direct contact with an operator. In this case, you will be asked to provide contact details for the person you are dealing with.

 

Mobile Connect extensions

This document describes the extensions to the core Mobile Connect products that are supported by the Indian operators. These extension are based upon the Mobile Connect v1.1 specification.

Scope

India specific scope values

Scope Description
mc_mnv_validate Bypass the Ts&Cs page (which otherwise is shown to unregistered Mobile Connect users). Here, login_hint is a mandatory parameter which needs to be populated with 12-digit mobile number in plain text. E.g., login_hint=MSISDN:919958712345 or login_hint=MSISDN_ENCR:a;sldkfjasdj;lfjdsalkjf;ldasjfj;dkaslfj. In case of login_hintvalue mismatch with MSISDN from the header the basic offnet authentication flow is used with MSISDN in login_hint. In case of a match, seamless authentication happens. Highly regulated. Offered only to trusted SPs.
mc_mnv_validate_plus Bypass the Ts&Cs page (which otherwise is shown to unregistered Mobile Connect users). Here, login_hint is a mandatory parameter which needs to be populated with 12-digit mobile number in plain text. E.g., login_hint=MSISDN:919958712345 or login_hint=MSISDN_ENCR:a;sldkfjasdj;lfjdsalkjf;ldasjfj;dkaslfj. In case of login_hintvalue mismatch with MSISDN from the header, an error response is returned to SP. In case of a match, seamless authentication happens. Highly regulated. Offered only to trusted SPs
mc_india_tc Similar in functionality as to openid scope except login_hint is a mandatory parameter with the mobile number to be provided in plain text. In case of mismatch between MSISDN from header and MSISDN entered in login_hint, then, login_hint provided in the authorisation request is used for following offnet flow.
mc_attr_vm_share User’s verified msisdn is shared.
mc_attr_vm_share_hash User’s verified msisdn is hashed and shared.

Scope usage

Scope mc_india_tc mc_mnv_validate mc_mnv_validate_plus
Scenario Developer/SP knows enduser's msisdn. Use login hint for verification if login hint does not match msisdn in header. Developer/SP knows enduser's msisdn.
Bypass Ts&Cs.
Developer/SP knows enduser's msisdn.
Bypass Ts&Cs.
Works only for on-net.
login_hint Mandatory. Plain text. Mandatory. Plain text. Mandatory. Plain text.
Off-net offnet offnet error
On-net (login_hint != to header MSISDN) offnet;
login_hint used for verification
offnet;
login_hint used for verification
error
On-net (login_hint = to header MSISDN) onnet onnet onnet

Notes

Additional scopes phone/mc_identity_phonenumber_hashed applicable with all aforesaid scopes resulting in msisdn in userinfo response as plain text (phone) or encrypted value (mc_identity_phonenumber_hashed).

offnet: USSD prompt / SMS fallback for user verification.

onnet: Automatic user verification using headers.

 

Discovery Modes

Discovery mode ‘none’

User on wifi: mc_india_tc / mc_mnv_validate / mc_mnv_validate_plus will show msisdn entry screen. User will enter msisdn and SP will get operator details and subscriber_id. Authorization call can be invoked using login_hint=ENCR_MSISDN:subscriber_id.

User on mobile data: mc_india_tc / mc_mnv_validate / mc_mnv_validate_plus will have discovery success using IP with no subscriber_id in response. Authorization call cannot be invoked in absence of any value to be put into login_hint.

Discovery mode ‘MCC/MNC’

User on wifi: mc_india_tc / mc_mnv_validate / mc_mnv_validate_plus will result in SP getting operator details but no subscriber_id. Authorization call cannot be invoked.

User on mobile data: mc_india_tc / mc_mnv_validate / mc_mnv_validate_plus will have discovery success using IP with no subscriber_id in response. Authorization call cannot be invoked.

India specific scopes will not work with MCC/MNC. However, for none, if user is on wifi, india specific scopes will work.

 

Sample Authorization Requests

mc_india_tc

http://india.gateway.wso2telco.com/authorize/v1/airtel/oauth2/authorize?client_id=x-88ae3b5d-18f1-c5-a97e- a6c5eae9cd5a&scope=openid+mc_india_tc+ mc_identity_phonenumber_hashed&response_type=code&redirect_uri=http://localhost:8080/MCIndiaDummy/callbac k&acr_values=2&nonce=12345&state=12345&login_hint=919958712345

mc_mnv_validate

http://india.gateway.wso2telco.com/authorize/v1/airtel/oauth2/authorize?client_id=x-883b5d-18f1-4fc5-a97e-
a6c5eae9cd5a&scope=openid+mc_mnv_validate+ mc_identity_phonenumber_hashed&response_type=code&redirect_uri=http://localhost:8080/MCIndiaDummy/callbac k&acr_values=2&nonce=12345&state=12345&login_hint=919958712345

mc_attr_vm_share

http://india.gateway.wso2telco.com/authorize/v1/airtel/oauth2/authorize?client_id=x-883b5d-18f1-4fc5-a97e-a6c5eae9cd5a&scope=openid+mc_attr_vm_share&response_type=code&redirect_uri=http://localhost:8080/MCIndiaDummy/callback&acr_values=2&nonce=12345&state=12345

mc_attr_vm_share_hash

http://india.gateway.wso2telco.com/authorize/v1/airtel/oauth2/authorize?client_id=x-883b5d-18f1-4fc5-a97e-a6c5eae9cd5a&scope=openid+mc_attr_vm_share_hash&response_type=code&redirect_uri=http://localhost:8080/MCIndiaDummy/callback&acr_values=2&nonce=12345&state=12345

mc_mnv_validate_plus

http://india.gateway.wso2telco.com/authorize/v1/airtel/oauth2/authorize?client_id=x-883b5d-18f1-4fc5-a97e- a6c5eae9cd5a&scope=openid+mc_mnv_validate_plus+ mc_identity_phonenumber_hashed&response_type=code&redirect_uri=http://localhost:8080/MCIndiaDummy/callbac k&acr_values=2&nonce=12345&state=12345&login_hint=919958712345