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

Provide a revoke API that terminates the link to a specific Site [enhancement] #779

Open
michael-s-crawford opened this issue May 27, 2022 · 4 comments

Comments

@michael-s-crawford
Copy link

Currently is it possible to revoke all remote access to the local site by running the skupper revoke-access command. It is requested that this functionality be extended to allow for a Site to specified in that command so that only that Site is revoked (and other pre-existing connections are maintained).

Furthermore, it would be desirable if this functionality was available to the Skupper Console (HTTP) API

@aii-nozomu-oki
Copy link
Contributor

aii-nozomu-oki commented Mar 30, 2023

Hi, any updates on this?

My rough ideas are below:

  • Implement Certificate Revocation List(CRL)
  • Implement OCSP
  • Use certificates with short expiration and repeat renewals automatically. The revoke API stops the automatic renewal process.

@fgiorgetti
Copy link
Member

Auto certificate renewal for already linked sites, seems like an interesting enhancement to explore.

@grs
Copy link
Member

grs commented Mar 30, 2023

I think CRLs are the most obvious way to implement a revoke function. Auto-renewal is certainly also interesting, but I would see that as a different feature.

@aii-nozomu-oki
Copy link
Contributor

To implement CRL, changes to skupper-router are required, aren't they?

Another issue is determining where to store the CRL.
K8s Secret is a simpler solution, but it has 1 MiB limitation.

References:
projectcontour/contour#4252
istio/istio#17763

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

No branches or pull requests

4 participants