Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
to-cdn-01 auth: 2017/06/23 19:31:59 auth.go:172: Legacy Login error: Post
https://remote_ip/api/1.2/user/login: x509: cannot validate certificate for
remote_ip because it doesn't contain any IP SANs Legacy URL:
https://remote_ip/api/1.2/user/login
I sanitized `remote_ip`
I think this is just the auth.go not havenât the same HTTP functionality
(with the keys) as the webfront.go
the `legacy-login-url` points to `https://remote_ip/api/1.2/user/login`
which is preventing me from getting a JWT token back
Just point your auth.go's 'legacy-login-url' to point an 'https' TrafficOps
and you'll see the problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
