-
|
I'm trying to connect our new RTSP client code to get a metadata feed but having some problems with authentication. When I send a SETUP request, I initially get a 401 Unauthorized response, as expected, and so I resend the request with added Authorzation header, with a digest computed from the realm and nonce values provided by the server. However. I always still get a 401 Unauthorized response. Can you confirm that this is the correct algorithm to use to compute the "response" field of the RTSP digest? Or is there anything else you think I might be doing wrong? Thanks in advance! Here's an example session: Request: Response: Resending Request: Second Response: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
I opened a helpdesk ticket (Case 02024790) for this. I guess it's an "ADP Partner program" ticket, but I can't tell. I do want to go through the proper channels, but we also have to lend the camera to another team at some point in the next couple days, so I'm hoping I can at least start getting a metadata feed by then, and capture some data from it, so that I can work on consuming the data. |
Beta Was this translation helpful? Give feedback.
-
|
Copying from other thread so I can mark it as the answer: "There was a bug in my code that was omitting 0's from hex strings. So something like 00 would be emitted as just 0. So when I built the digest values, this was making the digest incorrect. After fixing that, it seems to be working now. Definitely streaming something, so hopefully it's streaming what I need (once I parse it)." |
Beta Was this translation helpful? Give feedback.
Copying from other thread so I can mark it as the answer: "There was a bug in my code that was omitting 0's from hex strings. So something like 00 would be emitted as just 0. So when I built the digest values, this was making the digest incorrect. After fixing that, it seems to be working now. Definitely streaming something, so hopefully it's streaming what I need (once I parse it)."