...
a backend service that has an OCN-ready API
an OCN - Identity
the OCN - Identity of your selected OCN Node and a registration token (TOKEN_A in OCPI Terms)
...
If you are using the Command Line Interface provided in the OCN - Registry Repository on Bitbucket you can simply check the Public URL of your selected OCN Node by doing this:
...
The Public URL could look something like this: https://test-node.emobilify.com
Please visit the OCN - Registry Repository on Bitbucket for further details about this step.
...
Now we are ready to connect to the OCN Node. The credentials request is detailed below. Make sure to replace the variables TOKEN_A, TOKEN_B and PUBLIC_IP, PARTY_ID and COUNTRY_CODE where described. TOKEN_A should match the one generated for you by the faucet. TOKEN_B should match the authorization token that you have created. Meanwhile, PUBLIC_IP should point to your publicly accessible web service. Lastly, PARTY_ID and COUNTRY_CODE refer to the same OCPI credentials that you used when generating the registration token and entering details to the OCN - Registry.
| Code Block |
|---|
curl https://test-node.emobilify.com/ocpi/2.2/credentials \
-H 'Authorization: Token {{TOKEN_A}}' \
-H 'Content-Type: application/json' \
-d '{
"token": "{{TOKEN_B}}",
"url": "{{PUBLIC_IP}}/ocpi/versions",
"roles": [{
"party_id": "{{PARTY_ID}",
"country_code": "{{COUNTRY_CODE}}",
"role": "EMSP",
"business_details": {
"name": "Tutorial MSP"
}
}]
}' |
...