Media Browser Integration

[Svekke]

It's a two step process just like the xml interface

First you need to use /public/Util/NPVR/Client/Instantiate to get the sid and and the salt and then calculate clientKey according to the docs and the submit

/public/Util/NPVR/Client/Initialize/ClientKey?sid=....

You need to save the sid for all transactions but that is only for remote access

Martin

I did that. But then i get the previous error....
I also don't think you need to provide the sid. According the api only the ClientKey...

[mvallevand]

You need the sid when connecting remotely. That is the only reason for using these methods.

Can you give me the json from Instantiate and your PIN if not using 0000 and calculated clientKey I will see if they match what I calculate

Martin

[Svekke]

You need the sid when connecting remotely. That is the only reason for using these methods.

Can you give me the json from Instantiate and your PIN if not using 0000 and calculated clientKey I will see if they match what I calculate

Martin

In the initialize there is no option to add the sid...
On other calls it's possible but not in the Initialize.

I did the Instantiate calln, that works. I get my sid and salt back.
I also create the clientKey. It works with the xml method....
So the calculation must be OK...

[mvallevand]

Don't go by the Swagger dox. I tried without the sid and get a 401 However your 404 still looks like syntax. Does you URL look like mine? You don't actually use ?clientKey= in the URL it is the raw key ie

/public/Util/NPVR/Client/Initialize/a81c513a5770587ed1d8c5288e18da27?sid=49f506516c704822a73447fceb4ea499

Martin

[Svekke]

That's just the purpose of the swagger information.
To test everything....

The Initialize should that be a POST? I can't send any "RequestContent" for the clientKeys ...

[mvallevand]

It's a GET

Martin

[mvallevand]

I also create the clientKey. It works with the xml method....So the calculation must be OK...

Thinking about this while shoveling snow, UJB uses a different algorithm to create the hashed key so it is not exactly the same.

Martin

[UncleJohnsBand]

Thinking about this while shoveling snow, UJB uses a different algorithm to create the hashed key so it is not exactly the same.

Martin

I am assuming it is the same method as sub uses as it is exposed via the API and the instructions in the doc explain what needs to be done. What is not the same as the XML method sub provides?

I did miss having the sid as required in the API doc for the Initialize call.

I have updated the API do and put a patch on the FTP server for that fix: newa-enhanced_Initialize_API_patch_20140202-1.zip (make sure to flush your browser cache)

The initialize is not a Post it is a Get and the client key that you generate is passed on the path....not a query string as Martin indicated with the sid being passed in as a query string. /initialize/client-generated-key?sid=xxxxxx

[Svekke]

It's a GET

Martin

I know, it's a GET. But to send some content, isn't it better to use a POST instead of the GET?
Or am i missing something in the REST methodology?

[mvallevand]

I am assuming it is the same method as sub uses as it is exposed via the API and the instructions in the doc explain what needs to be done. What is not the same as the XML method sub provides?

It's not a big difference sub's client key is a parameter called &md5= and sid is required too.

Martin