Unauthenticated option to allow new Windows 10 discovery

[bfarmilo]

Hi there, I came across this project after looking for a way to connect my Rpi camera as an IP cam natively to Windows 10. This looks to be implemented about a year ago, see:

https://blogs.windows.com/windowsdeveloper/2019/10/10/connecting-network-cameras-to-windows-10-devices/

A key point seems to be at least initially, it doesn't support cameras requiring a username/pwd ("If the ability to pair to authenticated cameras with the Settings page is important for your use case, please let us know via the Windows Developer Feedback.").

I have the camera working well and can stream to VLC on my windows 10 machine using RTSP, but adding the camera using Windows as a device fails (it sees the camera, I click on it, windows shows 'Connecting' for a split second then no change, and no camera installed).

Until windows supports authentication, can someone point me to where I might look in this package to disable authentication? I'm happy to dig and to a PR but if you can point me in a direction it would be greatly appreciated.

Thanks

[RogerHardiman]

The username and password that us used for the ONVIF layer and the RTSP layer is in rposConfig.json If the username is "" and the password is "" it requires no authentication.

[AadityaRathod97]

How to authenticate username and password for the rtsp server. I tried with rpos config to set username and password but it works without username and password. how can i secure rtsp server.

[cptskippy]

The blog entry @bfarmilo mentioned has a utility for Device Enumeration and Pair using authentication. I've tried using this tool to add an rpos camera and it fails as well. Unfortunately Windows doesn't offer any further details and there's nothing in the Event Viewer to indicate what the trouble might be.

There's a footnote in the blog that makes me wonder if the lack of full ONVIF support might be the isse:

*ONVIF Profile S conformant cameras that don’t adhere strictly to the WS-Discovery protocol might have issues during discovery and enumeration.

@RogerHardiman, does rpos keep any sort of logs that I could examine to perhaps give us an indication of what Windows might be trying to do that is failing?

[TomGood75]

• Just thought I'd add I'm in the same situation as @RogerHardiman, if it gives looking into this any further weight. This looks like an awesome project, and I was looking for way to host a cam from an rpi directly to windows 10 via ONVIF, without some clunky middleware on the windows side to create a virtual webcam off rtsp/mjpg stream (for an app only supporting webcams). If there are any other updates/thoughts on this, that would be awesome, because it seems this project is so close...
• I was able to get everything up and running with rpos - and windows 10 discovers the cam - but won't connect as Roger ran into - without providing any indication as to why. It just briefly flashes 'connecting' and nearly immediately gives up on the connect attempt to the discovered device.

[RogerHardiman]

I'd forgotten all about this and never looked into it any more back in 2021. RPOS has lots at the Discovery and ONVIF level. Then the video comes via RTSP. We can use a couple of different RTSP servers, one from mpromonet (based on live555) and one from Oliver Schwaneberg (based on gstreamer). I've never tried to get either of them to dump out their RTSP logs. What works easier is to run Wireshark and look at the RTSP traffic (usually port 8554 for rpos).