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

API Security #8

Open
allynt opened this issue Sep 1, 2016 · 7 comments
Open

API Security #8

allynt opened this issue Sep 1, 2016 · 7 comments

Comments

@allynt
Copy link

allynt commented Sep 1, 2016

From @murphysj on January 15, 2014 18:4

WHO: Mark

Need to secure api with ssl certificate.

Copied from original issue: ES-DOC/esdoc-docs#43

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @momipsl on March 24, 2015 13:59

IPSL has obtained a server certificate but it's use would entail moving API to an IPSL server - not sure if we really want to do this at this time.

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @momipsl on March 24, 2015 15:35

Need to secure at HTTPS level and also enforce authentication

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @SebastienDenvil on March 25, 2015 14:29

How to enforce authentication by the end of May? We need a strategy document about that. For py-esdoc client first, then we will extent. If the CIM questionnaire wrap the pyesdoc-client then we win twice.

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @momipsl on March 25, 2015 14:45

This scenario is very different form the CIM Questionnaire. The focus here is securing the ES-DOC API publishing endpoints. I would suggest simple HTTPS digest authentication with an authenticator at the API which simply performs a whitelist check against a config file.

Thus when institute X wishes to leverage pyesdoc to publish documents the admin workflow is as follows:

  1. Institute X contacts ES-DOC support to request authentication.
  2. ES-DOC supports generate username / password which is added to authentication whitelist config file.
  3. ES-DOC supports sends credentials to institute X in an offline manner (a telephone call will suffice).
  4. Institute X updates local pyesdoc.json config file which is their responsibility to secure.

The above is very simple and will take a day or so to implement on the API side.

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @SebastienDenvil on March 25, 2015 14:50

Let's have a document describing this. Let's circulate this (es-doc-pi + wip). And then if we all agree and we know who will support that charge (es-doc support) then let's implement.

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @murphysj on March 25, 2015 17:9

Moving out of any milestone until this is better understood.

@allynt
Copy link
Author

allynt commented Sep 1, 2016

From @murphysj on April 3, 2015 14:27

Considered top priority in the Feb 2015 F2F

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant