-
Notifications
You must be signed in to change notification settings - Fork 0
feat: setup enclaved bitgo express with mTLS support #1
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
Conversation
46b3862 to
442c3ce
Compare
ef5c5a1 to
1e7dbfd
Compare
1e7dbfd to
daaa741
Compare
Ticket: WP-4352
0bbe17d to
efe92c4
Compare
efe92c4 to
00bdafa
Compare
| } | ||
|
|
||
| const fingerprint = clientCert.fingerprint256?.replace(/:/g, '').toUpperCase(); | ||
| if (!fingerprint || !config.mtlsAllowedClientFingerprints?.includes(fingerprint)) { |
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.
nice. this way our clients can use this in an even more secure way and restrict the certificates to ones they generate internally for usage only by express nodes
|
|
||
| ## License | ||
|
|
||
| MIT |
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.
do we have guidance/approval to use mit licesense ?
islamaminBitGo
left a comment
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.
LGTM overall, not seeing tests for mTLS setup with client and server certs and a constrained list of accepted certs by the server?
Yeah its only setup for dev/test env's rn. We can add those easily later |
WP-4352