Verifying SSO Login Webcheck

Ah, you’re stuck with the even more complicated method of the harder hard way, haha. Sorry, that’s not funny to you.

This gets really complicated because your FreshService is using MS as your IdP (SSO provider). So you’d have to configure multiple steps and one of those steps would have to reach out to MS using a service account to get a live token, then use that token to actually log in, then verify that the right content is on the page. You’re talking about Groovy scripting each step and running those tests from one of your collectors. It gets really messy.

Options:

1. Modify the requirement so that you’re testing pieces individually. Test that you can log in with a service account that doesn’t use SSO. Monitor MS SSO some other way. Assume that both working means both would work together.
2. Use Selenium (and the MS SSO plugin) to record you logging in. This will get you started with a Selenium script that you’d have to modify to get a complete login working. You’d then use Selenium grid to execute the transaction and monitor the result with LM. This was supposed to be part of the APM offering. LM may have realized that jumping into APM in the deep end wasn’t a good thing so they’re backpedaling a bit on APM. Ask your CSM about getting help monitoring Selenium. It may be that they can turn on a beta feature for you and monitor it directly, or they could at least provide DataSources (I know they exist) to monitor selenium execution results.
3. Write groovy code to execute each one of the steps and run it as an internal web check (I’ve never built one that complex, not sure many/any have).

tl;dr - LM is only ankle deep when it comes to their published features around synthetics. When you get to something this complicated, you’re sort of on your own, or you have to leverage something like Selenium.

Happy to continue this discussion, but you might want to see what your CSM can do for you first.