Failure in Duo module in v1.17.0
See original GitHub issueOnce I upgraded aws-adfs to v1.17.0 (via pip), I get errors extracting roles from response as I never get a Duo prompt to approve.
[authenticator authenticator.py:authenticate] [5158-MainProcess] [140522403542848-MainThread] - ERROR: Cannot extract roles from response
This account does not have access to any roles
Let me know what information I can collect, and how to get verbose output from aws-adfs.
OS: MacOS 10.14.5. Also happens with Ubuntu 18.04. Python version: 3.6.8 aws-adfs version with error: 1.17.0 from pip ADFS version 4.0 (10.0.14393.3053) (Windows Server 2016) Duo Connector version 1.2.0.17
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
How to interpret and troubleshoot Duo Authentication Proxy ...
The goal of this guide is to walk through some common Duo Authentication Proxy debugging scenarios in order to help techs better understand...
Read more >Configure Duo Two-Factor Authentication For Firepower ...
This document describes the steps required to configure external two-factor authentication for management access on Firepower Management ...
Read more >Duo | Authenticators - Curity
The Duo authenticator can be used to log users in using Duo, from Cisco. This service provides two-factor authentication using various methods, including:...
Read more >aws-adfs/CHANGELOG.md at master · venth/aws-adfs · GitHub
ERROR: Cannot extract roles from response #128; Failure in Duo module in v1.17.0 #126. Merged pull requests: lxml 4.4.0 dropped support for python...
Read more >Re: Samba 4.1.17 for ReadyNAS Duo v1 (sparc)
apt-get install --reinstall grep perl perl-modules apt-get remove samba-common libwbclient0 mkdir /run mkdir /run/samba mkdir ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same problem with v1.17.0. When I revert back to v1.16.0 everything is work fine again.
Reviewing the changes in 1.17.0, I don’t see anything that should impact Duo, but I don’t have a Duo environment to test against.
Can one/both of you try clearing out existing settings, logging in with ‘-v’ flag, and report back (be sure to review for ‘sensitive’ information before posting):
That will give a better idea of what’s going on.