cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
291
Views
1
Helpful
1
Replies

Android Cisco Secure Client versus Azure MFA w/ FTD error

steeda
Level 1
Level 1

Setup per guides online and the famous Youtube video. Windows client works fine, Android clears MFA with Approved, but then says

"The AnyConnect URI could be parsed". Here is some debug:

01-19 16:02:09.780 I/AnyConnect(11055): URIHandlerActivity: Received command: anyconnect://externalsso
01-19 16:02:09.784 E/AnyConnect(11055): URIHandlerActivity: Missing parameters, must specify both name and host. Cannot process the 'externalsso' action.
01-19 16:02:09.785 E/AnyConnect(11055): URIHandlerActivity: Invalid URI parameters: anyconnect://externalsso/AAEAAQBbMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWrSCzt8mwxgRKKaHNsLSVSY48AE360UV1DsURpy1H6MuLBX8CAj6Bu8PDQcxyPNsr6cMy4%2FoTd3o6x9xPzYMKQACAAx91%2F0ku3cOrp1BhUwAAwAY4JlAOiwtnUsOrG25B1Gz0NFVQOdytpEyAAQADOi9%2B5DUcFJVJwfXow%3D%3D
01-19 16:02:09.785 E/AnyConnect(11055): URIHandlerActivity: The AnyConnect URI could not be parsed.
01-19 16:02:09.785 E/AnyConnect(11055): Globals: Terminal error: The AnyConnect URI could not be parsed.

 

Both name and hose.... the XML profile has such. What's Android whining about?

 

1 Accepted Solution

Accepted Solutions

steeda
Level 1
Level 1

Bah, I had an outdated External SAML package. Installed external-sso-5.1.1.42-webdeploy-k9.pkg, mapped it to the Connection Profile, fixed.

View solution in original post

1 Reply 1

steeda
Level 1
Level 1

Bah, I had an outdated External SAML package. Installed external-sso-5.1.1.42-webdeploy-k9.pkg, mapped it to the Connection Profile, fixed.