Trying to implement SSO with Shibboleth in our enterprise.
Ran into issue where our Microsoft SAML server refuses to accept the request sent by Rancher:
MSIS0018: The SAML protocol message cannot be read because it contains data that is not valid. --> System.FormatException: String was not recognized as a valid DateTime.
Seems that Rancher writes timestamp in more detail than Microsoft can handle. It looks like the reason may lay within the very nature of the DateTime-structure in .NET which is based on 100-nanosecond, but would it be possible to add configuration for the format of the timestamp?