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

Updates node API to support JWT SVID #544

Merged
merged 1 commit into from
Jul 23, 2018

Conversation

azdagron
Copy link
Member

  • Adds JWT methods to node API and renames things to clearly distinguish
    between JWT and X509
  • Updates agent client to support fetching JWT SVIDs
  • Provides server stub

Fixes #495

- Adds JWT methods to node API and renames things to clearly distinguish
between JWT and X509
- Updates agent client to support fetching JWT SVIDs
- Provides server stub

Signed-off-by: Andrew Harding <azdagron@gmail.com>
Copy link
Member

@evan2645 evan2645 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

string spiffe_id = 1;

// List of intended audience
repeated string audience = 2;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Side note: any thoughts on where token lifetime might get configured?

Copy link
Member Author

@azdagron azdagron Jul 23, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

expiration isn't part of x509-SVID CSR's and the expiration is configured in one of two ways:

  1. Agent SVID's get the default TTL
  2. Workload SVID's get a TTL based on the registration entry.

I intended JWT-SVID's to follow suit.

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

Successfully merging this pull request may close these issues.

None yet

2 participants