Note: JWT was selected to align with CCC. Keystone supports OAuth1 as well, this has not been tested.
files endpoint for repo file submission
all posts call stub publish() method, eventually this should call kafka
/v0/files
Passthrough proxy to act as an authorization check for all DCC server api calls
/* any other request is passed to DCC. This release does not enforce authorization
Testing
Is very preliminary at this time. The tests that do exist are integration tests, that is they test the API with the backends, no mocks exists. Therefore, real databases need to exist and the server needs to be able to connect to them. Since LDAP servers are often behind firewalls, travis is not possible at this time.
API
Features:
/v0/login, /v0/logout
/v0/files
Passthrough proxy to act as an authorization check for all DCC server api calls
/*
any other request is passed to DCC. This release does not enforce authorizationTesting
Is very preliminary at this time. The tests that do exist are integration tests, that is they test the API with the backends, no mocks exists. Therefore, real databases need to exist and the server needs to be able to connect to them. Since LDAP servers are often behind firewalls, travis is not possible at this time.
TODO
The dcc portal will need screens to /login & /logout
The proxy will need to implement filters & redaction previously prototyped in javascript.