Github user amiryesh commented on the issue:

    https://github.com/apache/incubator-trafficcontrol/pull/567
  
    Hi,  glad to hear you are taking the effort of using the GW.
    Did you get to see webfront/README.md or auth/README.md?
    
    The auth server is responsible for login. The auth readme explains how to 
obtain a token, which I understand that you did.
    
    The webfront server is the API GW. The webfront readme shows token usage 
example:
    $ curl --insecure -H'Authorization: Bearer <token>' -Lkvs 
https://localhost:8080/ds/
    
    At phase 0, auth server access tm_users, user_role and role_capabilities DB 
tables to compose a JWT with the user's capabilities. However, all webfront 
configuration is hard coded. The forwarding rules are hard coded in ruls.json 
and the authorization data (route-to-capability mapping) is hard coded in 
routes.json.
    
    Please check your routes config, and make sure your API calls are done 
against the webfront server and not the auth server.
    
    If you are still having problems, please attach your query samples + 
console output from both webfront.go and auth.go



---
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.
---

Reply via email to