[GitHub] incubator-trafficcontrol pull request #697: Adds triggers missed by mysql->p...
GitHub user dangogh opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/697 Adds triggers missed by mysql->postgres migration You can merge this pull request into a Git repository by running: $ git pull https://github.com/dangogh/incubator-trafficcontrol missing-triggers Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/697.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #697 commit 27dd3cee9c4d047091a5ba64a09fdca5b3400ed0 Author: Dan Kirkwood Date: 2017-06-23T16:14:15Z fix missing triggers -- lost in mysql to psql transition commit 470c86600d97ccdfd7144bcdcce2dd85a9f4c331 Author: Dan Kirkwood Date: 2017-06-23T21:52:10Z add copyright header --- 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. ---
[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...
Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/567 Attempted to centralize the points: - [ ] Bug: 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 - [ ] Both SHA1 and scrypt needs to be support (or just go through the API instead - [ ] --- 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. ---
[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...
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. ---
[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...
Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/567 Carried forward from slack for reference: Password format changed from SHA1 to scrypt. http://search.cpan.org/~mik/Crypt-ScryptKDF-0.006/lib/Crypt/ScryptKDF.pm https://github.com/apache/incubator-trafficcontrol/commit/3dd1ad0c84adbebe6b3b514e61658c4eac648d50 GitHub Change TO password hashing to scrypt · apache/incubator-trafficcontrol@3dd1ad0 incubator-trafficcontrol - Mirror of Apache Traffic Control (incubating) https://godoc.org/golang.org/x/crypto/scrypt godoc.org Package scrypt Package scrypt implements the scrypt key derivation function as defined in Colin Percival's paper "Stronger Key Derivation via Sequential Memory-Hard Functions" (http://www.tarsnap.com/scrypt/scrypt.pdf). --- 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. ---
[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...
Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/567 @amiryesh I think I discovered another issue. When you send the Mojo cookie now, it flows through to Traffic Ops accordingly, but should we also need the "capabilities" guard against that backend as well. I think you've built the capabilities for only JWT and the "Claims". You need to authorize "all" routes against capabilities, not just JWT routes. --- 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. ---
[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...
Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/567 @amiryesh Another useful piece of information would be timings. For example: "How long did it take to call that backend, in milliseconds?" --- 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. ---
[jira] [Closed] (TC-376) Steering services feature additions
[ https://issues.apache.org/jira/browse/TC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Gelinas closed TC-376. Resolution: Implemented Assignee: Derek Gelinas > Steering services feature additions > --- > > Key: TC-376 > URL: https://issues.apache.org/jira/browse/TC-376 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops >Reporter: Derek Gelinas >Assignee: Derek Gelinas > Labels: configuration, steering > > Steering services need to be able to set order or weight for their targets. > Order can be any whole integer, weight must be a whole integer equal or > greater than 0. > We also need to provide the ability to add more than 2 targets per steering > service. > Documentation on Steering Services > http://trafficcontrol.apache.org/docs/latest/admin/quick_howto/steering.html?highlight=steering%20service -- This message was sent by Atlassian JIRA (v6.4.14#64029)