-
Notifications
You must be signed in to change notification settings - Fork 101
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
Version 0.3.9 returns no roles #50
Comments
Please check if you have AWS_PROFILE enviromental variable set. If it's set then unset it. If it's feasible perform also: aws-adfs reset --profile=default Then please repeat the login attempt. |
ok
rolled it back
thanks for your help with this |
Hi, I noticed that in the posted code you use binary from /home/quixand and /home/nick Is it a typo? Does any hint given by me helped you fix the issue? |
no that was just a failure of my obfuscation find and replace I discovered this problem because I installed it for the first time on my mac (v10.12.6) and had the same issue, I thought I had done something wrong so installed on a fresh copy of debian stretch in virtualbox and got the same problem. That was when I suspected a bug and came looking here. |
Hi @quixand, in order to reproduce the issue, I used the docker container built on the top of Debian stretch version. Relevant files you can find here: Dockerfile and docker-compose.yml I brought up aws-adfs by command: If I could ask you to help me with investigation of the issue, please use docker description provided by me via gist and after |
This issue is already solved. The solving commit is: 2178cf5 |
Hi
ive just installed on a clean debian 9 stretch (vm) install and got the following (some credentials redacted)
So I rolled back with
which seemed to fix it. I saw bug #44 I'm guessing its related
thanks
The text was updated successfully, but these errors were encountered: