07-25-2018 07:24 AM - edited 07-25-2018 07:27 AM
Hello,
I'm testing SAML authentication using Azure AD as IdP and the ASA as the SP. Login works fine but the logout fails because the ASA is sending the wrong URL.
Although I've configured the valid URL:
url sign-out https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0
Looking at the requests performed by the browser during the logout, the URL requested is:
https://login.microsoftonline.com/common/wsfederationwa=wsignout1.0 without the '?' so the browsers receives a not found error from the server.
Anyone has this working with Azure?
Regards.
09-04-2018 02:21 AM
Good Morning Antonio, I'm looking at this configuration for a client who's looking to add Azure as a IdP against their ASA's currently deployed, could you forward any reference documentation you found for this design ? Everything I've discovered so far references either using on-prem MFA server or the NPS extension
Any pointers would be greatly appreciated.
09-05-2018 06:50 AM
Hello,
I followed these two references below from MS and Cisco. Anyway, I hopefully plan to blog the whole process shortly. I'll update the post upon I post it.
https://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-custom-apps
Good luck!
08-26-2020 08:24 AM
09-23-2020 02:50 AM
Hi all,
When you check the URL in the ASA, you will see the question mark in URL is missing.
This is because when entering / pasting commands into CLI the help function is being activated when '?' is signaled.
Just before manually entering the '?' in the string you have to press CTRL+V. Now the question mark is being added.
After re-applying the 'saml identity-provider' command in your tunnel-group the SSO sign-out also works
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