I realize this is niche, but if you go to set up SSO in your environment, heaven help you. My crew just got through a week of getting things set up. There were 3 of my employees and at least 1 Innovative support staff and 1 Innovative dev involved all week. I can't imagine the amount of $$$ that was burned in hourly staff time getting it going. And of course the good news is that an upgrade or server move could break it all again! Some of the documentation is wrong and some of the transcribing of the data from the documentation leads to errors. Yes, if you leave off a trailing "/" it can cause the whole thing to break.

One thought that might work to improve this is if Innovative hosted a setting generator on their site. That way you could pick your set up type and plug in your values and then it could spit out the proper .json files. If there happened to be something incorrect in the config file generation, rather than having to update the documentation and wait on that whole process, including the fact that it probably won't be updated until the next version of Polaris roles out, even if it is a simple typo which would lead to additional customer frustration.
On the other hand the config generator hosted by innovative could just be updated so that all configurations going forward from there would work just fine.

Even if this process doesn't work, there has to be a better most cost effective way to perform the SSO set up tasks.