Recently active topics

Hi team,I have previously read through some older posts about implementing SSO for Rundeck Community version and it seems this is only available for Commercial/Enterprise versions.However, I’d like to know if we have alternatives to do that on Community. I saw some posts suggesting pre-auth mode, how could we implement it or even implement other solutions to have SSO on our environment?

Join us for the next installment of release notes on August 12th, where Forrest will share what is new in version 6.1.0! Mark your calendar to watch live:​​​​​Youtube LinkedIn

As we are now planning to upgrade from MySQL 8.0 to 8.4 with Rundeck 6.0.1 supporting it, are there plans yet for supporting MySQL 9.7?

Previously I reported a CVE associated with Log4J Log4jLink.  This was resolved with the release of 6.0.  Thanks!  Almost immediately after I upgraded to 6.0, I got flagged on a new CVE:  Plugin Name:  Apache Log4j 2.13.1 < 2.25.5 / 2.26.0 < 2.26.1 Improper JSON Serialization (CVE-2026-49844)Plugin Output:  Path              : /var/lib/rundeck/bootstrap/rundeck-6.0.0-20260629.war  Installed version : 2.25.4  Fixed version     : 2.25.5Is there a plan for upgrading the Log4J version again?  Please advise. Thanks,Eric

I recently opened a ticket for rundeck 5.10.0 integration with vault which got resolved but same is not working for rundeck 5.19.0 version  In Rundeck version 5.10.0, I installed the Vault plugin by navigating to:**Rundeck UI → Settings → Plugins → Find Plugins → Vault → Install**I then uploaded Vault Storage Plugin version 2.0.1 from UIhttps://github.com/rundeck-plugins/vault-storage/releases/download/2.0.1/vault-storage-2.0.1.jarlogged in to the Rundeck server, I replaced the existing plugin file by renaming the uploaded JAR:```mv vault-storage-2.0.1.jar vault-storage.jar```The Rundeck UI continued to show the Vault plugin as installed, and the integration worked as expected.However, when I followed the same process in Rundeck version 5.19.0, it did not work. After running:```mv vault-storage-2.0.1.jar vault-storage.jar```the Rundeck UI showed that the Vault plugin needed to be installed.Under **Key Storage**, I also received the following error:```Error: Cannot get property 'pluginG

Catching up on the latest month + what's coming next! Highlights 😎 Summer Watch GuideAre you responsible for keeping systems running 24/7? Let PagerDuty handle everything in the background while you relax in the sun, lounge by the pool, or enjoy the beach. Watch these quick on-demand sessions on your phone right from your lounge chair: Slack Experience Upgrades - All-new incident management capabilities in PagerDuty’s Slack App: Quick Declare, automated incident channels, new interactive /pd commands SRE Agent - Meet your new virtual responder that enables teams to achieve autonomous operations through automated triage and investigation  Shift-Based Schedules - From layer-based architecture to a flexible system that natively scales with modern engineering teams and naturally fits their workflows. 👉 Register now to the next PagerDuty Live Behind the Scenes: Post-Incident Reviews 🍦  Ice Cream, Patio Games, and On-Call Talk in SFJoin us on July 29 for the Duty Free Summer Patio - a

The PagerDuty Mobile App documentation for iOS (https://support.pagerduty.com/main/docs/mobile-app-settings#configure-ios-devices) states:"When you are added as a Responder to an incident, the iOS mobile app will always use the PagerDuty Alert ringtone for push notifications."Could you explain why this behavior is implemented? Why can't responder notifications use the same custom notification sounds as other push notifications?Are there any plans to make this configurable in future releases?

We have multiple services connected to the same Slack Notification Channel.Historically, when an incident was reassigned between those services, the existing Slack incident card was updated, including the Service field. Recently, without any configuration changes on our side, PagerDuty began posting a second incident card for the same incident when the service changes.Interestingly, subsequent incident updates (we use the Thread incident updates option) are still applied to the original Slack post rather than the newly created one. This suggests that PagerDuty is still able to correlate the Slack message with the incident, making the additional post redundant.Expected behaviorReassigning an incident between services that are connected to the same Slack Notification Channel should update the existing Slack incident card, including the Service field.Actual behaviorA second Slack incident card is posted when the service is reassigned. Subsequent incident updates, such as status changes, c

Hi Team,I am setting up rundeck with Hashi Corp Vault, as part of setup process and testing found below issues, If anyone overcame these, please let me know the workaround steps.Rundeck version installed: 5.10.0Issues: I tired installing vault plugin, but rundeck did not recognize this plugin, so i ended up installing from Rundeck UI. Vault Storage Plugin version installed: 1.2As per rundeck documentation, this supports KV Engine V2, if we add parameter “rundeck.storage.provider.1.config.engineVersion=2” but this plugin is still using only KV engine V1. Once all the configuration is completed, restarted rundeck service, and was able to make successful connection to vault and able to see the keys, but as per our environment, we kept the vault token expire for 5 mins, once this expired rundeck is not auto using the new vault automatically. When rundeck lost connection to the vault due to token expiry, all jobs are failing irrespective if the jobs are using the keys from vault in the jobs

Hello.I noticed there is a weird difference between the two timestamps shown in Rundeck 5.19 web interface.I’m referring tot he HH.mm:ss timestamp shown in the left sidebar, which I assume to be the server’s timestamp in local timezone and the ISO8601 timestamp shown in tooltip/.rdlog file. The problem is they look inconsistent so I was wondering how each of these timestamps is determined The timestamp form tooltip/.rdlog file has a Zulu suffix which suggest UTC but there is a huge inconsistencyThe server is located in France (UTC + 2), locale timezone is set correctly in the OS, so is the UTC clock. NTP synchronization is active. Therefore on Rundeck server, both local timezone and UTC are set correctly.Rundeck JVM is executed with the correct timezone parameter “-Duser.timezone=Europe/Paris”. But the problem is there is much more than 2 hours differences between the left sidebar timestamp and the ISO8601 tooltip timestamps.I noticed the issue issue in job during it’s execution on the

I’m trying to set up a filter to show incidents trigger outside of core business hours. But the business hours interruptions filter variable doesn’t show it’s accepted values/how to use it. It explains here what business hours mean but not what the value should be below: