07-13-2022 09:30 AM
I have one network working with AnyConnect using SAML and Azure AD and it works as expected. Users can connect using their Azure AD credentials and things seems to be great there. When I've tried to set up any second site, there is no prompt for authentication at all, just a successful connection message and they are truly connected. I have deleted and recreated and Azure application and retested it. I currently have a case open about this issue but wanted to see if anyone else in the community has run into this or might have a clue for me. Thanks for any replies.
Solved! Go to Solution.
07-26-2022 02:31 PM
Could have been firmware related. In 16.16.2+ and 17.7+ firmware versions a change was made to set the Forceauthn= value to true in the SAML request sent by the MX to the Identity Provider. This means that each time a user tries to re-authenticate, user credentials will be required. Prior to this change users were able to disconnect and reconnect to the VPN without credentials within a given time - if the user's auth token was considered still valid by the Identity Provider.
07-13-2022 01:29 PM
Are you using the default port or a different port?
07-13-2022 01:33 PM
Default.
07-13-2022 02:00 PM
One thing I noticed that confused me was that once a user connected successfully to Azure AD it seems to remember it and not prompt for the multifactor. It freaked me out a little. It is kind of like the o365 MFA it doesn't require MFA if the user has recently authenticated via MFA.
07-13-2022 02:02 PM
The original network I set this up with prompts every time. Any new network I try to set up with AnyConnect and SAML never prompts, even the first time.
07-13-2022 05:55 PM
I don't think you can use the same cisco anyconnect enterprise application with different anyconnect servers
07-13-2022 06:01 PM
I think you're correct but I haven't seen definitive documentation on that. To be clear, this is a second discrete application from the first network.
07-28-2022 11:18 AM
You can't share enterprise applications. You need an AnyConnect enterprise application for each MX head end.
07-28-2022 11:50 AM
I do have an enterprise application for each MX. I did try sharing one at one point, but that is not what is causing this behavior now. Now it seems that the Forceauthn= value isn't being set to True by the MX. The MX is picking up on an Azure token rather than forcing authentication at connection time.
07-14-2022 09:39 AM
Update: Azure application sign-in logs for both locations give successful authentication results and each knows the identity of the user(s). Both logs claim that the first and second factors are satisfied by an existing token, but again, one network prompts for credentials every time and other one never does.
07-17-2022 01:49 PM
One thing to note about SAML is that it is an SSO technology (single sign-on). To spell this out further - if a user is already signed on, they don't have to sign in for any other SAML app - single sign-on.
Most likely, in this case, the user has already SAML authenticated to something else, and hence Azure is not making them authenticate again.
More than likely, you are experiencing normal and correct operation.
07-18-2022 08:14 AM
Thanks for the reply! I agree and think you are correct that this would, under most circumstances, be normal behavior. The mystery in this case is that there are two networks, with two Azure applications, and they behave differently. "Network 1" prompts for credentials, including MFA, every time. "Network 2" never prompts for credentials at all. The sign-on log in Azure shows the same authentication successes for both networks. So, I can connect to network 1 by entering all credentials, then disconnect, and connect right back, and I am still prompted for credentials. i could then disconnect from network 1 and connect to network 2 and not be prompted. I could disconnect and reconnect to network 2 repeatedly and not be prompted. if I go back to network 1, I am prompted again, including for the second factor.
07-18-2022 01:25 PM
What is the Azure session length configured for network 2? Perhaps try dropping it to 1 hour. Another option, go into network 2, and force sign out the user.
The user doesn't have a FIDO token (like a Ubikey) for network 2 plugged into their computer's USB port?
It sounds to me like the user is not already logged into network 1 (and gets prompted) but is signed into network 2 (and is not getting prompted).
07-18-2022 06:38 PM
I did not deliberately configure either application's session length and don't even know where to look for that.
I am one of the users for this and use my own account for testing the authentication. I do not have any FIDO tokens and I am testing both from Windows and iOS.
Networks 1 and 2 refer to my Meraki networks, so I assumed "disconnecting" the VPN client also "logged out".
07-25-2022 08:30 AM
We replaced the MX in the affected network for another reason, and that solved this issue as well. I am still not certain what went wrong with the MX, but I wanted to update this in case anyone else runs into the same issue and comes here looking for answers.
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