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

v1.0.6 breaks API 1.0 authentication #22

Open
1 task done
db0 opened this issue Mar 22, 2021 · 0 comments
Open
1 task done

v1.0.6 breaks API 1.0 authentication #22

db0 opened this issue Mar 22, 2021 · 0 comments
Labels

Comments

@db0
Copy link

db0 commented Mar 22, 2021

Summary

The latest collection seems to be breaking backwards compatibility with API 1.0 instances.

The following (copied from the official examples) doesn't work anymore in 1.0.6 but it works in 1.0.5

- name: Logon - Not use_shared_logon_authentication
  cyberark_authentication:
    api_base_url: "{{ web_services_base_url }}"
    username: "{{ password_object.password }}"
    password: "{{ password_object.passprops.username }}"
    use_shared_logon_authentication: no

Steps to Reproduce

Using 1.0.6 Run the example authentication against API 1.0 SAM Vault server

Expected Results

Authenticate and retrieve token in ansible_facts

Actual Results (including error logs, if applicable)

fatal: [server]: FAILED! => {"changed": false, "headers": {"Content-Type": "application/json"}, "msg": "Error while performing authentication.Please validate parameters provided, and ability to logon to CyberArk.\n*** end_point=https://sam.example.com/PasswordVault/API/Auth/CyberArk/Logon\n ==> HTTP Error 403: Forbidden", "payload": "{\"username\": \"USERNAME\", \"password\": \"********\"}", "status_code": 403}

Reproducible

  • Always

Version/Tag number

  • Ansible v. 2.10
  • collection v1.0.6

Additional Information

It seems that the wrong URL is sent with 1.0.6. It is sending to /PasswordVault/API/Auth/CyberArk/Logon when it should be sending to /PasswordVault/WebServices/auth/Cyberark/CyberArkAuthenticationService.svc/Logon. I.e. it is not detecting which API version is being used.

@db0 db0 added the kind/bug label Mar 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant