-
Notifications
You must be signed in to change notification settings - Fork 0
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
Set up docs container #7
Conversation
The moved files are from the 'eligibility-server' project and were originally moved from the 'benefits' project. docker-compose.yml needed a small change with the build context in order for the 'COPY docs/requirements.txt ...' to work properly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! I was able to get all this running locally after the tiny change to the Compose file (see below).
I requested some minor reorganization of the content in anticipation of having usage/code docs in addition to the specification.
docs/token-signing-encryption.md
Outdated
|
||
The Eligiblity Verification API makes use of Signed and Encrypted JSON Web Tokens (JWS, JWE, JWT) as a means of data transfer. | ||
|
||
A public/private keypair must be generated by each party (Benefits Client and Eligibility Verification Server). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make this more generic here:
A public/private keypair must be generated by each party (Client and Server).
docs/token-signing-encryption.md
Outdated
The Eligiblity Verification API makes use of Signed and Encrypted JSON Web Tokens (JWS, JWE, JWT) as a means of data transfer. | ||
|
||
A public/private keypair must be generated by each party (Benefits Client and Eligibility Verification Server). | ||
[Example keys](https://github.com/cal-itp/benefits/tree/dev/localhost/keys) are included for the test verification server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expand to point to example keys in both benefits
and eligibility-server
docs/token-signing-encryption.md
Outdated
|
||
There are two new files: | ||
|
||
* `[file name].key`: private key in PEM format, apply to a `TransitAgency` instance in Django |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again we can make this a little more generic:
private key in PEM format, needed by the Client only
docs/token-signing-encryption.md
Outdated
* `[file name].pub`: public key in PEM format, give to the Eligibility Verification server | ||
|
||
A public key in PEM format from the Eligibility Verification server is also required, and must be applied to an | ||
`EligiblityVerifier` instance in Django. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Client also requires a public key from the Eligibility Verification server, so this process must be repeated to generate the Server's keypair.
The Server's private key should not be shared.
Thanks for the feedback @thekaveman . I pushed new changes - let me know if anything looks off. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📖 📑 📚
What this PR does
docs
container that starts upmkdocs
docs
folder