Few HTTPS SharePoint URLs are not working in CA App Synthetic Monitor says "(401) Unauthorized"
Below are the migrated URLs which was not working whereas the same works through the browser using the given credentials.
Kindly assist and let me know in case of any further information required.
Supply Chain Sharepoint Sites6:- http://site6.intranet/sites/SCG --> Site migrated to SP2019 so please change this URL as https://intranet.site6.com/sites/SCG
Supply Chain Sharepoint Sites:5- http://site5.intranet/sites/SC --> Site migrated to SPO so please change this URL as https://site5.sharepoint.com/sites/SC
Release : 10.4
Here is how ASM works with HTTPS monitors.
1. HTTPS are simple monitors. They go to the site and see if it is up. (i.e. www.mysite.com). If a site requires a login before reaching the target URL, then you would use the username and password fields in the advanced section of the monitor settings.
2. If a site requires an access request wherein a code must be sent to another email (example: access to www.mysite.com requires a code to be sent to [email protected] and then verified), then an HTTP/HTTPS monitor will not suffice. You would need a script monitor (written in JMeter or Webdriver)., However the main issue with this is it requires extensive scripting on your part (or your Sharepoint team) as Broadcom does not write the scripts. We can have a Services Engagement attempt to write it for you. You probably would have more control by using an OPMS in this case as our Public Stations are just pass throughs to run the checks and do not do any intelligent handling such as 3rd party verification codes.
3. To monitor intranet sites, you must use our OPMS to become the bridge between the internet (to reach ASM) and the intranet (to reach your internal site behind your corporation's firewall). The OPMS runs on Linux. You can find the OPMS installer here (https://asm.ca.com/en/products/downloads).
You can also find more information about OPMS's here. Please review the pre-installation checklist to follow which Linux flavors are supported as well as hardware, software, network access and access rights requirements.