Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have found more businesses using content delivery networks sharing IP address space with each other. Let's say business partner ACME is using public ip address 23.5.5.4 and want to see our traffic coming from a specific source address. In the past ...
We acquired some MR33s and moving them to our dashboard. I frequently have problems with registration even though I was able to add them to inventory and to a specific network. To troubleshoot I've run packet captures of the switch port of the MR33. ...
I tried to add an MR33 for the first time to my dashboard due to an acquisition. It gave me an error that I needed to disable NBAR to do so - disable Analytics. After I got the MR33 added back to the network I found that I was able to re-enable the a...
I have a large copy job and I noticed that maximum throughput is listed at 600Mbps. If I turned off some of the inspection services might it be possible to get closer to the 1Gbps? This is inside to outside traffic flow. Thank you.
We've acquired another company with several recently purchased and to-be-deployed MS switches (and MRs). How can we get their licensing to be valid in our dashboard. We have Co-Term licensing and I'm not sure what there's is. Thank you.
debug webspn ssl is showing a signature mismatch issue. Something with the cert - or the import method perhaps?[SAML] consume_assertion:PHNhbWxwOlJlc3Bvb....ybWF0aW9uRGF0YSBJblJlc3BJul 15 12:28:26 [Lasso] func=xmlSecOpenSSLEvpSignatureVerify:file=/lo...
The "Reply URL" refers to what is sent back from Azure to the ASA, correct? I don't see anything called "Reply URL" within the ASA so I'm assuming that's the case.
I removed the SAML Identity Provider info in ASDM and recreated it. Now the MFA request is getting to Azure. But the authentication failed due to retrieval of single sign on cookie.
The result of removing the /SAML is that browser window pops up but now a message "Can't reach this page. Make sure https://https is correct." appears. I went back to Edit SSO Server parameters to make sure I didn't somehow include an https:// prefix...