You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The behaviour with secure option with default values changed when using values stored in key storage, in the rundeck 2.6.2 version.
In the past, when we used secure options with default value explicitly set in the “Default value” field the option itself might have been Required or Not – both settings used to work.
Now, if we move our default secure options to the key storage, we must choose Required=No otherwise the job fails.
The main issue we have with this is the case when the user does not have access to the key stored in the key storage but the job will start even if the option has no value.
The text was updated successfully, but these errors were encountered:
The behaviour with secure option with default values changed when using values stored in key storage, in the rundeck 2.6.2 version.
In the past, when we used secure options with default value explicitly set in the “Default value” field the option itself might have been Required or Not – both settings used to work.
Now, if we move our default secure options to the key storage, we must choose Required=No otherwise the job fails.
The main issue we have with this is the case when the user does not have access to the key stored in the key storage but the job will start even if the option has no value.
The text was updated successfully, but these errors were encountered: