03-23-2021 07:20 AM
Hi,
for a customer i'm trying to authenticate anyconnect using an AD, but i can't get it work. On the Cisco ASA is see the following messages:
Mar 23 15:02:07 [SAML] consume_assertion: The identifier of a provider is unknown to #LassoServer. To register a provider in a #LassoServer object, you must use the methods lasso_server_add_provider() or lasso_server_add_provider_from_buffer().
Mar 23 15:02:07
[SAML] consume_assertion:
[saml] webvpn_login_primary_username: SAML assertion validation failed
What do does messages mean? Could it be that the wrong saml idp url is being used or is it something else?
On the ASA we are running 9.8(4)29
03-23-2021 10:21 AM
If you made any changes to the SAML section after associating it with your tunnel-group (connection profile in ASDM), you have to remove and re-apply it. The #LassoServer errors are often a result of that issue.
03-24-2021 12:28 AM
Hi Marvin,
i already did that by removing and adding the saml identity-provider url in the tunnel-group webvpn-attributes, but that didn't resolve the issue
tunnel-group AD-SAML webvpn-attributes
no saml identity-provider <url>
saml identity-provider <url>
03-25-2021 03:57 AM - edited 03-25-2021 04:00 AM
Is this setup authenticating via an Azure AD instance?
03-26-2021 12:25 AM
we are using a local AD for authentication. In the future it will be an Azure AD
03-26-2021 01:26 AM
Given that, I would suspect the wrong SAML iDP URL is being used.
03-29-2021 07:41 AM
Customer is using a Microsoft ADFS with the following url:
saml idp https://xx.yy.zz/adfs/services/trust
03-30-2021 06:20 AM
I've never set it up with on-premise but in Azure it works fine.
I did find this guide for integrating a different app (Atlassian) with on-premise AD FS SAML. You should be able to follow most of the steps in it to work with your ASA:
03-29-2022 11:47 PM - edited 03-29-2022 11:54 PM
Hi Marvin,
i am having issue with integrating Azure MFA with ASA anyconnect.
No webpage was found for the web address: https://vpn1.company.com/+CSCOE+/SAML/SP/ACS?tgname=Azure-MFA
Mar 30 17:29:24 [SAML] get_lasso_signature_method:
Use SHA256 in SAML Request
Mar 30 17:29:24 [SAML] saml_add_config: SAML config added to list
SAML AUTH: SAML hash table cleanup periodic task
Public archive directives retrieved from cache for index 1.
Mar 30 17:29:37
[SAML] build_authnrequest:
https://login.microsoftonline.com/23e274fb-1240-4362-9b03-6b133e33c70e/saml2?SAMLRequest=fVLLTsMwEPyVyPfEsd0m1GorhT6kSoAQIA5ckJtuqCXHDl6nPL4eJwipHOA6O7M7M%2FYcVWs6WfXhaO%2FgtQcMyXtrLMpxsCC9t9Ip1CitagFlqOV9dX0leZbLzrvgamfImeR%2FhUIEH7SzJNmtF%2BSZbTe5K...
[SAML] saml_is_idp_internal: getting SAML config for tg Azure-MFA
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
SAML AUTH: SAML hash table cleanup periodic task
ANy idea what i am missing?
03-30-2022 01:26 AM
It's hard to say without a live troubleshooting session. What procedure did you follow for the setup?
03-30-2022 08:13 AM
03-30-2022 08:33 AM
03-31-2022
07:27 AM
- last edited on
04-17-2025
09:13 AM
by
rupeshah
I have attached the logs here.
Now my previous issue is cleared.
but now i'm getting Anyconnect "Authentication failed due to unexpected error". after succesful login with Microsoft.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide