On Wed, Dec 4, 2019 at 2:40 PM James Ralston <ralston@xxxxxxxxx> wrote: > When testing a connection, after I supply my username/password, I am > prompted for a secondary authentication code. After entering "push" > (which pushes an approval request to my phone), and approving the > push request on my phone, openconnect immediately dies with this > error message: > > Unhandled Pulse authentication packet, or authentication failure > > …followed by 3 lines of hex-dumped data. > > Is this a known issue? Ping? Is there anything I can do to help debug this, or implement the missing functionality? This is a showstopper for --protocol=pulse for sites that use Duo MFA (and perhaps any form of MFA) with Pulse, and MFA is becoming increasingly more common. So I'd like to help get this working if I can. _______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
