Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shibboleth request timestamp format #9953

Closed
oliverorav opened this issue Sep 27, 2017 · 1 comment
Closed

Shibboleth request timestamp format #9953

oliverorav opened this issue Sep 27, 2017 · 1 comment
Labels
area/access-control kind/enhancement Issues that improve or augment existing functionality

Comments

@oliverorav
Copy link

Rancher versions:
rancher/server: v1.6.5
rancher/agent: v1.2.5

Infrastructure Stack versions:
healthcheck: v0.3.0
ipsec: v0.1.0
network-services: v0.2.0
scheduler: v0.5.1

Docker version: (docker version,docker info preferred)
Version: 1.12.5
API version: 1.24
Go version: go1.6.4
Git commit: 7392c3b
Built: Fri Dec 16 02:23:59 2016
OS/Arch: linux/amd64

Server:
Version: 1.12.5
API version: 1.24
Go version: go1.6.4
Git commit: 7392c3b
Built: Fri Dec 16 02:23:59 2016
OS/Arch: linux/amd64

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Red Hat Enterprise Linux Server release 7.3 (Maipo), 3.10.0-693.1.1.el7.x86_64

Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node with external MariaDB.

Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle

Issue
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 vs. nanoseconds in Go (7 floating points vs 9 floating points).

Would it be possible to add configuration field to change/alter the precision of the timestamp?

@aemneina aemneina added area/access-control kind/enhancement Issues that improve or augment existing functionality labels Oct 8, 2017
@loganhz
Copy link

loganhz commented Oct 5, 2018

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.

@loganhz loganhz closed this as completed Oct 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/access-control kind/enhancement Issues that improve or augment existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants