Unanswered questions

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: 

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

Hi allLooking for help pinning down where Scribe's transcript routing is decided.Setup:- Production incident is declared in PagerDuty, which kicks off an Incident Workflow.- The workflow creates a Zoom meeting, then creates a dedicated Slack channel for the incident, then adds the PagerDuty Advance Scribe Agent. Scribe joins the Zoom call and posts the live transcript to Slack.Problem:- The Scribe transcript is being posted to our `#alerts` channel (where all our alerts land), instead of the dedicated incident channel created by the workflow.What I've already checked:- Workflow action ordering is correct "Create a Slack Channel for an Incident" runs before "Add PagerDuty Advance Scribe Agent."- Scribe Agent settings have no option to select a target Slack channel.- The "Add PagerDuty Advance Scribe Agent" workflow action also has no channel/surface input.Questions:1. What determines which Slack channel/surface Scribe posts the transcript to? 2. If we have `#alerts` mapped to the servic

See title

Within Rundeck, is it possible to restrict the ip source/locations for an api key to be used?  For instance, the “admin” userid’s api key can only be used by scripts/calls from the Rundeck server itself.  Any suggestions on how to restrict the source calling location of specific api keys (as normal regular end-users’ api keys can be from their laptops and such)?

Hi Team,I’m configuring Azure SSO (OAuth2) for Rundeck using the official documentation:https://docs.rundeck.com/docs/administration/security/sso/azure-sso.html I have successfully created an Application Registration in Azure AD and configured the required values in my rundeck-config.properties file.However, after restarting the Rundeck server, the changes are not taking effect.When I access: https://rundeck.company.com/it redirects to: https://rundeck.company.com/user/logininstead of initiating the Azure SSO flow. Current rundeck-config.properties file Configuration: # rundeck-config.properties: Azure SSOrundeck.sso.loginButton.enabled=truerundeck.sso.loginButton.title=Login with Azurerundeck.sso.loginButton.url=oauth/azure rundeck.security.oauth.azure.autoConfigUrl=https://login.microsoftonline.com/<DIRECTORY_TENANT_ID>/v2.0rundeck.security.oauth.azure.clientId=<CLIENT_ID>rundeck.security.oauth.azure.clientSecret=<SECRET_VALUE>rundeck.security.syncOauthUser=true# Az

After setting rundeck.security.apiCookieAccess.enabled to value of “false”; the “Projects” list pull-down shows an empty list after user’s log into the Rundeck gui.  Granted, the Rundeck home page still shows all the projects.  (Rundeck version 5.20.0)

After upgrading to Rundeck 5.20.0; it looks like the ssj-ssh plugin no longer works with double-quoted commands in the job steps.  For example, the following used to work:<exec>sudo "sh /u01/scripts/sre/myscript.sh ${option.parm1}"</exec> We had to change it to the following in order for it to work:<exec>sudo sh /u01/scripts/sre/myscript.sh ${option.parm1}</exec>With double-quotes, the job returns: [sudo] password for user1:sudo: sh /u01/scripts/sre/myscript.sh userval1: command not found[user1@serverxyz ~]$ echo $?1 Note: This is on Oracle Linux 9 server.