...
Validate state for a Bokskya account by ddsId or email.
URL |
| ||||
Method |
| ||||
Request | Authorization | Required | The token acquired from the Authentication Service. Example: | ||
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 |
| ||||
Returns |
| OK (Will also be returned if user not found, see response body) | |||
| On error | ||||
Curl examples
Example of successful response based on email address:
...
Create a new DDS Bokskya user account
URL |
| ||||
Method |
| ||||
Request | Authorization | Required | The token acquired from the Authentication Service. Example: | ||
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) | |||
Content-type | Required | application/json | |||
JSON attributes | Required | Email of the user (unique in bokskya) | |||
name | Required | First name of the user (minimum length 2) | |||
surname | Required | Surname of the user (minimum length 2) | |||
Response |
| ||||
Returns |
| OK | |||
| On error | ||||
Curl example
Example of successful creation of user:
| Code Block | ||
|---|---|---|
| ||
$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 OK
Content-Type: application/json;charset=UTF-8
{"id":"743a3b25-e71f-4544-82c7-b5e66358b08a","active":true} |
Auth user by partner
| Status | ||||
|---|---|---|---|---|
|
Service to authenticate a Bokskya account on behalf of a user and to support Bokskya implementation of Adobe Content Server VendorID.
URL |
| ||||
Method |
| ||||
Request | Authorization | Required | The token acquired from the Authentication Service. Example: | ||
Date | Required | The timestamp the request was made. Must comply with RFC 1123 date formats. Example: | |||
Accept | Required | application/json (We recommend all new implementations to use this header, XML support will be phased out in the future) | |||
Response |
Note: id attribute is base64 encoded token for authenticated {ddsId} (AQIC5wM2LY4SfcwrQoJ9lw3nFA39ppf8X8KAdIxmd4ldHUI. | ||||
Returns |
| OK | |||
| On errors | ||||
Get adobeId
| Status | ||||
|---|---|---|---|---|
|
Look up AdobeID for a Bokskya account by ddsId or email
URL |
| ||
Method |
| ||
Request | Authorization | Required | The token acquired from the Authentication Service. Example: |
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 | When request is valid, user found and adobeId exist:
When request is valid, user found and adobeId not exist
| ||
Returns |
| OK | |
| On error | ||