Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure options with defaults in key storage #1657

Closed
ltamaster opened this issue Feb 3, 2016 · 0 comments
Closed

Secure options with defaults in key storage #1657

ltamaster opened this issue Feb 3, 2016 · 0 comments
Labels
Milestone

Comments

@ltamaster
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants