MIP Driver Credentials - Factory Default

ChristophAcs · February 11, 2026, 11:25am

Background: I built an RTMP MIP driver that doesn’t load any external devices, so no username or password is required.

Issue/Question:

When I add a new device and leave “Use factory default credentials” checked, I get an unauthorized response (or the error shown in the screenshot). However, if I enter any other username/password combination, it works.

Is this a bug, a limitation, or a known behavior?

My code is open source, here is my connection manager:

github.com/Cacsjep/mrtmp_device_driver

RTMPDriver/DriverFramework/RTMPDriverConnectionManager.cs

f86187828


      
          private RtmpServer _rtmpServer;
          private int _currentPort;
          private readonly object _restartLock = new object();
          
          internal RtmpServer RtmpServer => _rtmpServer;
          
          public RTMPDriverConnectionManager(RTMPDriverContainer container) : base(container)
          {
          }
          
          public override void Connect(Uri uri, string userName, SecureString password, ICollection<HardwareSetting> hardwareSettings)
          {
              if (_connected)
                  return;
          
              int port = 8783;
              var portSetting = hardwareSettings?.FirstOrDefault(s => s.Key == Constants.ServerPort);
              if (portSetting != null && int.TryParse(portSetting.Value, out int parsedPort))
              {
                  port = parsedPort;
              }

I also can’t find anything in the logs that explains why this fails.

Big Thanks

Peter_Posselt_Vergmann · February 13, 2026, 7:07am

Have you tried adding some logging in your connect method and see what it is called with? I don’t remember exactly what is passed to the driver when the Factory defaults is selected by the user, but I suspect it might be something you don’t handle well (maybe null).

ChristophAcs · February 13, 2026, 7:12am

@Peter_Posselt_Vergmann thanks for you replay =)

yes but short tests show that i dont come to this point, looks like this is for interal driver only, and internal something exists for factory credentials for an existing driver like AXIS, but this kinda of definition is not implemented in MIP driver framework. I dont check the creds at all. So when the are null i dont care because no code touches it.

Peter_Posselt_Vergmann · February 13, 2026, 7:32am

I just tested with DemoDriver on XProtect 2025 R3 and it worked fine. There is no way of providing factory defaults from a MIP Driver so they will always be empty, but if I set up my DemoDriver device to accept empty user name and password it connected fine.

Peter_Posselt_Vergmann · February 13, 2026, 7:36am

I just realized that you are probably not selecting the driver in the dialog where you provide IP and credentials (so “(Auto-detect)” is selected)? If I do the same I can reproduce.

I will report this with the team but as it is a bit of an edge cage I cannot say when it will be fixed.

ChristophAcs · February 13, 2026, 7:39am

I tested it now with adding emtpy creds, and this seams to work, also both cases, either “auto detect” or manual selecting it

Peter_Posselt_Vergmann · February 13, 2026, 7:41am

But please confirm whether your issue with “Factory default” is when you have “(Auto-detect)” selected?

ChristophAcs · February 13, 2026, 7:41am

You are correct, factory fails with auto detect but not when selected.

Fails: Factory Creds - Hardware Model (Auto-Detect)

OK: Factory Creds - Hardware Model (My Driver)

Thank you thats very good input, it should be more like: when only one driver is selected, auto detect option should be at all no visible, and just my driver is selected, because this confused me and also other folks =)