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
{{ message }}
This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
I had a working AWX instance with LDAP integration. I used tower-cli receive --all to export AWX data. I then nuked the existing AWX instance and re-deployed a new AWX instance and did a tower-cli send. After this was done, I could no longer login with my LDAP user. I made sure to set LDAP bind password correctly after tower-cli send. After deleting my user in AWX, I could login with my LDAP user.
Steps to reproduce:
Do tower-cli receive --all > assets.json from a working AWX instance with LDAP integration
Deploy a new and fresh AWX instance
Do tower-cli send assets.json against new AWX instance
Try to log in as one of your LDAP users
Please make tower-cli export users in such a way that they are created in a new AWX instance completely similar to where they came from such that LDAP logins continue to work after a receive/send.
The text was updated successfully, but these errors were encountered:
We had the same issue... To overcome it, we had to set the ldap_dn directly in the database ( in main_profile ) and delete the password ( in auth_user )
Best regards,
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I had a working AWX instance with LDAP integration. I used tower-cli receive --all to export AWX data. I then nuked the existing AWX instance and re-deployed a new AWX instance and did a tower-cli send. After this was done, I could no longer login with my LDAP user. I made sure to set LDAP bind password correctly after tower-cli send. After deleting my user in AWX, I could login with my LDAP user.
Steps to reproduce:
Please make tower-cli export users in such a way that they are created in a new AWX instance completely similar to where they came from such that LDAP logins continue to work after a receive/send.
The text was updated successfully, but these errors were encountered: