...
curl -i -H "Accept: application/json" -H "Authorization: Boknett TGT-28905-pOzdvVr50wpTMl10DooFrDjTarMdwkeRzhlJ4KcMrQfEl13fxK-login.boknett.no" -H "Date: Thu, 13 Aug 2015 12:16:39 GMT" 'https://idp.dds.boknett.no/validate/ola.nordmann@norge.no' HTTP/1.1 200 OK {"id":"212c60f9-57db-4b5b-b32a-ed561346eda1","active":true} |
Example of request where user does not exist:
curl -i -H "Accept: application/json" -H "Authorization: Boknett TGT-28905-pOzdvVr50wpTMl10DooFrDjTarMdwkeRzhlJ4KcMrQfEl13fxK-login.boknett.no" -H "Date: Thu, 13 Aug 2015 12:16:39 GMT" 'https://idp.dds.boknett.no/validate/kari.nordmann@norge.no'HTTP/1.1 200 OKDate: Thu, 13 Aug 2015 12:24:30 GMT Content-Type: application/json;charset=UTF-8 Content-Length: 25 {"data":"USER_NOT_FOUND"} |
Register Account
Create a new DDS Bokskya user account
| URL | https://idp.dds.boknett.no/register | ||
| Method | POST | ||
| Request headers | Authorization | Required | The token acquired from the Authentication Service. Formated "Boknett TGT-...." |
| Date | Required | The timestamp the request was made. Must comply with RFC 1123 date formats. Example: Tue, 10 Jun 2014 16:23:42 GMT | |
| Accept | Required | application/json (We recommend all new implementations to use this header, XML support will be phased out in the future) | |
| JSON attributes | Required | Email of the user (unique in bokskya) | |
| name | Required | First name of the user | |
| surname | Required | Surname of the user | |
| Response body | {"id":"743a3b25-e71f-4544-82c7-b5e66358b08a","active":true} | ||
| Returns | 200 | OK | |
| 40X | On error | ||
Curl example
Example of successful creation of user:
$curl -i -H "Accept: application/json" -H "Content-Type: application/json" -H "Authorization: Boknett TGT-29061-mbdeGwDnbGTJ4qlSv4IYTm5Cpu5iDO1XxOSgg2IPAXNPhGEa0v-login.boknett.no" -H "Date: Thu, 13 Aug 2015 14:40:00 GMT" -d '{"email":"ola.nordmann@norge.no","name":"Ola","surname":"Nordmann"}' "https://idp.dds.boknett.no/register"HTTP/1.1 200 OKContent-Type: application/json;charset=UTF-8 {"id":"743a3b25-e71f-4544-82c7-b5e66358b08a","active":true} |
...
| URL | |||
| Method | GET | ||
| Request headers | Authorization | Required | The token acquired from the Authentication Service. Formated "Boknett TGT-...." |
| Date | Required | The timestamp the request was made. Must comply with RFC 1123 date formats. Example: Tue, 10 Jun 2014 16:23:42 GMT | |
| Accept | Required | application/json (We recommend all new implementations to use this header, XML support will be phased out in the future) | |
| Response body on success | {"id":"QVFJQzV3TTJMWTRTZmN3clFvSjlsdzNuRkEzOXBwZjhYOEtBZEl4bWQ0bGRIVUkuKkFBSlRTUUFDTURFLio="} Note: id attribute is base64 encoded token for authenticated {ddsId} (AQIC5wM2LY4SfcwrQoJ9lw3nFA39ppf8X8KAdIxmd4ldHUI. | ||
| Returns | 200 | OK | |
| 40x | On errors | ||
AdobeId
...
Look up AdobeID for a Bokskya account by ddsId or email
| URL | |||
| Method | GET | ||
| Request headers | Authorization | Required | The token acquired from the Authentication Service. Formated "Boknett TGT-...." |
| Date | Required | The timestamp the request was made. Must comply with RFC 1123 date formats. Example: Tue, 10 Jun 2014 16:23:42 GMT | |
| Accept | Required | application/json (We recommend all new implementations to use this header, XML support will be phased out in the future) | |
| Response body on success | When request is valid, user found and adobeId exist: {"adobeid":"adobeId..."} When request is valid, user found and adobeId not exist {"data":"NO_ADOBEID_EXIST"} | ||
| Returns | 200 | OK | |
| 40x | On error | ||
...