MFA - Allowing URL

RahulPrasadh
Getting noticed

MFA - Allowing URL

We need to allow certain URL for accessing new MFA url, I have added URL to layer 3 outbound policy and whitelisted in content filtering and still unable to access, Is there any different config we need to do for allow new MFA url? 

am-landing.i2.automate-webservices.com/?hac=H90AAWOK&userFullName=Amy Scaggs&username=awruck01

5 Replies 5
alemabrahao
Kind of a big deal

alemabrahao_0-1740750772802.png

Have you run a URL test to validate the category in which the URLs are classified?

Remember that after adding the URLs to the whitelist you need to wait a few minutes for it to actually be applied.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
alemabrahao
Kind of a big deal

Check it out.

 

 

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering#Patter...

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
RahulPrasadh
Getting noticed

Yes, tested category and it's allowed and added to allow URL but still we are unable to access.

alemabrahao
Kind of a big deal

Try another way to add the URL, without HTTPs, with an asterisk in a part of the URL without pointing to the entire URL.

one of these ways will surely work.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
MaghM
Meraki Employee
Meraki Employee

If you notice the shared link shows the New URL which is:  https://fde-nonceapi-b2b-prd-na-gkf3gmc8amfbckcy.a01.azurefd.net

 

For example: " *fde-nonceapi-b2b-prd-na-gkf3gmc8amfbckcy.a01.azurefd.net/health "

 

Here is the documentation for reference:

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering

 

Allow 10-15min to make sure the changes took affect. 

If the issue is still ongoing, change the policy to one of the affected clients to be allow-list as this will bypass all the Meraki rules, check the below documentation if you are unsure how to apply it, scroll down to "using client list":
https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing...

 

Wait 10-15min and recheck if it works then check the other applied policies in the network. If still the same check the upstream devices.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
Get notified when there are additional replies to this discussion.