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

PSM service name variable is wrong - Correct name is cyber-ark privileged session manager. #143

Open
aglerj opened this issue Dec 7, 2023 · 0 comments

Comments

@aglerj
Copy link

aglerj commented Dec 7, 2023

Describe the bug
The psm_service_name variable in defaults>main.yml is incorrect, which causes automation to stop mid-way. The PSM service name should be cyber-ark privileged session manager, NOT cyberark privileged session manager.

To Reproduce
Steps to reproduce the behavior:

  1. run PSM automation
  2. psm software is installed, sets the psm_exists variable, however since the service name is spelled wrong, it stops here. As the psm service name doesn't match whats in the playbook.3.

Expected behavior
Using the correct PSM service name allows the PSM install pb to move on/work correctly.

Screenshots
n/a

Environment(please complete the following information):

  • Ansible version - n/a
  • Deployment environment - on-prem, but would impact all.
  • Version [e.g. 22] - v12.6 PSM installs

Additional context
If the PSM service name changes in newer PSM versions, maybe the pb can be adjusted to check for either service naming, old or new.

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

No branches or pull requests

1 participant