Why build SAMLtest?
Setting up a two new federated providers simultaneously is always tricky. Having a known, operational provider fixes half of the equation, making it much easier to get a new federated environment in place.
A service once called TestShib used to fill this need, but there were several occurrences that resulted in the need to build something new if the community wanted the same service.
We think we’ve also cleaned up the experience a lot and made it easier for you to accomplish your trusted federated transaction. The back end has been cleaned up, and we are free of years of deferred maintenance with no established repair mechanism except volunteers.
Signet thought it was time to build robust SAML test providers with a solid foundation. If you have suggestions on how to improve SAMLtest, please write.