Web API Error

[jcole998]

I rely quite a bit on the ability to submit commands via the web API. I'm testing V5 for compatibility with the commands that I use to set new recordings in V4. The command was submitted and resulted in the indicated error. Just before I submitted this thread, I tried it again and this time is worked! I can't seem to pin down what was different between the two trials.

Can you suggest what's going on?

- Receiving this error from the submitted command:
11:36:34 Command: http://localhost:8867/services/service?method=recording.save&event_id=3060918&directory_id=Hallmark&pre_padding=1&post_padding=3
11:36:34 Program "A Beautiful Place to Die: A Martha's Vineyard Mystery" NOT scheduled: Error code 8, Invalid Session.

[mvallevand]

You seem to be forgetting the sid that we already discussed https://forums.nextpvr.com/showthread.ph...#pid526152

Also remember there is a developer sub forum to help keep these posts organized better.

Martin

[jcole998]

You're right, Martin. I looked at that thread again(broken links in #7 and #20) and I will try the NScriptHelper items that sub suggested.

JC

[jcole998]

Still trying to get info from V5 through a login session with pincode "0000" from the example shown in the NextPVR post "Simulate old CommandLineOptions."

After getting a successful response for the session.initiate request, I tried to establish a V5 web session using the web API:

session.initiate response
stat sid                              salt                               
---- ---                              ----                               
ok  90e4bce9be9c473ea03ea84d2d21ab4b cbf08981-1720-4750-a44d-c8f5fd4c946e

session.login command:

http://localhost:8867/service?method=session.login&sid=90e4bce9be9c473ea03ea84d2d21ab4b&md5=AEE2BA545CC6D46951CCF863ED235D90

Response was:

StatusCode        : 200
StatusDescription : OK
Content          : <?xml version="1.0" encoding="utf-8" ?>
                    <rsp stat="fail">
                      <err code="1" msg="Login Failed" />
                    </rsp>
                   
RawContent        : HTTP/1.1 200 OK
                    Content-Length: 107
                    Content-Type: text/xml
                    Date: Sun, 16 Feb 2020 16:39:45 GMT
                    Server: Kestrel
                   
                    <?xml version="1.0" encoding="utf-8" ?>
                    <rsp stat="fail">
                      <err code="1" msg="L...
Forms            : {}
Headers          : {[Content-Length, 107], [Content-Type, text/xml], [Date, Sun, 16 Feb 2020
                    16:39:45 GMT], [Server, Kestrel]}
Images            : {}
InputFields      : {}
Links            : {}
ParsedHtml        : System.__ComObject
RawContentLength  : 107


The &md5 parameter was an MD5 hash of:

$md5In = (":" + $HashPin.Hash + ":" + $xmlRespInit.rsp.salt)
$md5In = ":4A7D1ED414474E4033AC29CCB8653D9B:cbf08981-1720-4750-a44d-c8f5fd4c946e"

I checked the MD5 codes against an online MD5 hash generator and they matched.

I am quite unfamiliar with V5 logs so I'm hoping the logs can tell you what's causing the failure.

Thanks.

[sub]

From memory, I think your pin hash needs to be lower case.

[jcole998]

No joy, sub. Where do I look in the log file?

[sub]

This is a bit of C# code that successfully logs in:

Code:

WebClient client = new WebClient();
var initiateXML = client.DownloadString(server + "/service?method=session.initiate&ver=1.0&device=scripthelper");                

XmlDocument doc = new XmlDocument();
doc.LoadXml(initiateXML);

string tempSID = doc.SelectSingleNode("/rsp/sid").InnerText;
string tempSalt = doc.SelectSingleNode("/rsp/salt").InnerText;

MD5CryptoServiceProvider md5Provider = new MD5CryptoServiceProvider();
byte []pinData = md5Provider.ComputeHash(Encoding.ASCII.GetBytes(pin));
string pinMD5 = BitConverter.ToString(pinData).Replace("-", "");

string combined = ":" + pinMD5.ToLower() + ":" + tempSalt;
                
byte[] data = md5Provider.ComputeHash(Encoding.ASCII.GetBytes(combined));
string expectedMD5 = BitConverter.ToString(data).Replace("-", "");

var loginXML = client.DownloadString(server + "/service?method=session.login&sid=" + tempSID + "&md5=" + expectedMD5);
if (loginXML.Contains("<rsp stat=\"ok\">"))
{
    sid = tempSID;
}
else
{
    Logger.Debug("Unable to login");
}

[jcole998]

Thanks, sub. I'll try again.

[jcole998]

I'm finally having success! Thanks for your patience. I can now ask for pending recordings and schedule new ones. The door is open!

May I ask a few more questions...

For how long does a session last?
Should I initiate a new session and new login with each series of requests?
Can I test if a session(SID) is still usable?

Thanks, again.

[sub]

From memory it'll last a couple of hours since the last call, unless you restart the recording service.

Realistically, I'd just login at the time you need to make any requests of the server, rather than trying to remember the side and use it over a period of time.