Azure SSO Admins Cannot Schedule Downtime

[clangbecker]

Installed the new 1.2 update today and was able to successfully add all users under SSO.

One thing that was observed prior to the 1.2 update from those accounts that could be added via SSO, none of them can schedule downtime for any hosts/services. AD and local accounts are able to perform scheduled downtime, but not SSO admins.

Anyone else seen this?

[bbahn]

Hi @clangbecker,

So you're saying that admins configured with SSO prior to 1.2 are unable to schedule downtime? Is your XI instance updated to 1.2? I just configured an admin user via SSO on my 1.2 machine and had no trouble scheduling downtime. Have you seen anything in your PHP logs when they attempted this?

[clangbecker]

Not quite, We could not add admin users via SSO prior to the 1.2 update due to an issue in the SSO implementation ( I have a previous thread on here that outlines that) so these are new SSO accounts that have been added after we upgraded to 1.2 and none of them (6 out 6) can schedule downtime. They can go through the steps and submit schedules but they never show up in the UI.

I will have to check the php logs and have them try again.

Thanks
CJ

[clangbecker]

so I had one user try and schedule downtime that does not end up ever showing up in the scheduler page. Found this error that popped in the ssl_error log as soon as she hit the "schedule downtime" button

[Thu Mar 05 08:07:32.477958 2026] [proxy_fcgi:error] [pid 5642:tid 140648812365568] [client 172.26.90.100:63500] AH01071: Got error 'PHP message: PHP Warning: Undefined variable $ts in /usr/local/nagiosxi/html/includes/utils-time.inc.php on line 68; PHP message: PHP Warning: Undefined variable $ts in /usr/local/nagiosxi/html/includes/utils-time.inc.php on line 68', referer: https://is-nagiosxi-east.gwl.com/nagios ... &type=host

[clangbecker]

Also captured this in the recurring downtime log

Checking recurring config id: 247c77b2093be84a1819e7686398fe41
Thu, 05 Mar 2026 08:01:02 -0700 hostgroup: ITS-UNIX-Pforms-Prod, services: yes
Thu, 05 Mar 2026 08:01:02 -0700 **************************************************************

Thu, 05 Mar 2026 08:01:02 -0700 get_next_scheduled_time('23:55', 'sat,sun', '', 'jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec') called
Thu, 05 Mar 2026 08:01:02 -0700 current_timestamp: 1772722862, 2026-03-05 08:01
Thu, 05 Mar 2026 08:01:02 -0700 candidate_timestamp: 1772780100, 2026-03-05 23:55
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_day_of_week: thu, checking: sat,sun
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_month_of_year: mar, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
Thu, 05 Mar 2026 08:01:02 -0700 check successful
Thu, 05 Mar 2026 08:01:02 -0700 candidate_timestamp: 1772866500,2026-03-06 23:55
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_day_of_week: fri, checking: sat,sun
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_month_of_year: mar, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
Thu, 05 Mar 2026 08:01:02 -0700 check successful
Thu, 05 Mar 2026 08:01:02 -0700 candidate_timestamp: 1772952900,2026-03-07 23:55
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_day_of_week: sat, checking: sat,sun
Thu, 05 Mar 2026 08:01:02 -0700 check successful
Thu, 05 Mar 2026 08:01:02 -0700 got candidate_month_of_year: mar, checking: jan,feb,mar,apr,may,jun,jul,aug,sep,oct,nov,dec
Thu, 05 Mar 2026 08:01:02 -0700 check successful
Thu, 05 Mar 2026 08:01:02 -0700 all parameters match, re-adjusting candidate for proper time
Thu, 05 Mar 2026 08:01:02 -0700 candidate_timestamp: 1772952900000, 2026-03-07 23:55
Thu, 05 Mar 2026 08:01:02 -0700 Downtime exists with start_time: 1772952900, and duration 3600 seconds ..
Thu, 05 Mar 2026 08:01:02 -0700 NOT SCHEDULING
Thu, 05 Mar 2026 08:01:02 -0700 Downtime exists with start_time: 1772952900, and duration 3600 seconds ..
Thu, 05 Mar 2026 08:01:02 -0700 NOT SCHEDULING
Thu, 05 Mar 2026 08:01:02 -0700 Downtime exists with start_time: 1772952900, and duration 3600 seconds ..
Thu, 05 Mar 2026 08:01:02 -0700 NOT SCHEDULING
Thu, 05 Mar 2026 08:01:02 -0700 Downtime exists with start_time: 1772952900, and duration 3600 seconds ..
Thu, 05 Mar 2026 08:01:02 -0700 NOT SCHEDULING
Thu, 05 Mar 2026 08:01:02 -0700 Finished Processing Downtime: Removing Lock File

[bbahn]

Interesting. I haven't been able to reproduce this, but I'll see if I can figure out what's going wrong here. Does this issue only ever happen with those configured via SSO and is it consistent?

[bbahn]

@clangbecker,

I have got in a fix for PHP message: PHP Warning: Undefined variable $ts in /usr/local/nagiosxi/html/includes/utils-time.inc.php on line 68 and fixed a bad comparison where the scheduled downtime feature was comparing minutes to seconds, which may be the cause of your inability to generate new downtime, though it'd hard to say for certain. These will be referenced in the Nagios XI changelog as [GL:XI!2328] and [GL:XI!2329].