Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

Introduce a built-in HTTP(S)-based provider #54

Closed
michaelklishin opened this issue Jan 17, 2017 · 1 comment
Closed

Introduce a built-in HTTP(S)-based provider #54

michaelklishin opened this issue Jan 17, 2017 · 1 comment
Assignees
@hairyhum
Labels
effort-low enhancement
Milestone
3.6.7

Comments

@michaelklishin
Copy link
Member

Now that #1 is merged, we should introduce a built-in provider that uses HTTPS.

Some concerns we have after a team-wide discussion:

  • What format should the certificate listing provider function expect? A list of JSON objects of a specific format (eventually maybe even a JWS/JW* one)? Should a list of new line-separated certificate URLs be returned by an HTTPS endpoint?
  • Should we use server certificate/key pair for HTTPS connections or a separate pair?
@michaelklishin michaelklishin added this to the 3.6.7 milestone Jan 17, 2017
@michaelklishin
Copy link
Member Author

@uvzubovs do you have an opinion on the above? Thank you.

@michaelklishin michaelklishin changed the title Introduce a build-in HTTP(S)-based provider Introduce a built-in HTTP(S)-based provider Jan 17, 2017
@michaelklishin michaelklishin modified the milestones: 3.6.x, 3.6.7 Jan 31, 2017
hairyhum pushed a commit that referenced this issue Feb 6, 2017
HTTP provider for trust store
cbe352f 
Fixes #54

Provider will list certificates as JSON, requiring list of objects
with `id` and `url` fields.
JSON root is an object with a single `certificates` field, containing
a list of certificate objects. (some web services require json root to
be object)
Certificates are loaded as PEM encoded files.
hairyhum pushed a commit that referenced this issue Feb 7, 2017
HTTP provider for trust store
542e958 
Fixes #54

Provider will list certificates as JSON, requiring list of objects
with `id` and `url` fields.
JSON root is an object with a single `certificates` field, containing
a list of certificate objects. (some web services require json root to
be object)
Certificates are loaded as PEM encoded files.
hairyhum pushed a commit that referenced this issue Feb 8, 2017
HTTP provider for trust store
1da61e8 
Fixes #54

Provider will list certificates as JSON, requiring list of objects
with `id` and `url` fields.
JSON root is an object with a single `certificates` field, containing
a list of certificate objects. (some web services require json root to
be object)
Certificates are loaded as PEM encoded files.
@hairyhum hairyhum mentioned this issue Feb 8, 2017
Merged
@michaelklishin michaelklishin modified the milestones: 3.6.7, 3.6.x Feb 10, 2017
@michaelklishin michaelklishin mentioned this issue Feb 10, 2017
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hairyhum hairyhum

Labels
effort-low enhancement
Projects
None yet
Milestone
3.6.7
Development

No branches or pull requests
2 participants
@michaelklishin @hairyhum