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

Certificates are only renewed at exact expiration date #300

Closed
maksokami opened this issue Oct 18, 2021 · 5 comments
Closed

Certificates are only renewed at exact expiration date #300

maksokami opened this issue Oct 18, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@maksokami
Copy link

Right now in 1.2.3 certificate renewal will only happen once at the expiration. Source: aziot-identityd - identity.rs.
This is not practical at all for IIoT devices that are often deployed in places with unreliable connectivity. With such approach renewal is likely to fail, while automatic renewal is also a key feature many customers were waiting for.

A much better approach would be to start repeated attempts to renew, when certificate is about 80-90% expired. Then, if first renewal attempt failed, next one can be scheduled in X weeks/x days, and the closer the expiration date the more frequent attempts should be. If this will not be the default behavior, at least there should be an option to enable it.

@arsing
Copy link
Member

arsing commented Oct 18, 2021

Yes, it was the plan that identityd would renew the device ID cert on a timer some time before it expires (same with certd and the EST ID cert). But it looks like we never got around to implementing it.

@arsing arsing added the bug Something isn't working label Oct 18, 2021
@maksokami
Copy link
Author

maksokami commented Oct 18, 2021

Any timeline and planned identityd version where it will happen will be greatly appreciated =)

@xirami
Copy link

xirami commented Dec 7, 2021

We're just discussing the same, would be super to have option to set in config.toml interval in days before expiration (when renewal attempt starts).
Curious question - when x509 is issued by EST, does IoT Edge still need user/password to EST for renewal of the certs or is it using existing issued certificate to authenticate renewal?

@arsing
Copy link
Member

arsing commented Dec 7, 2021

cc @gordonwang0 @onalante-msft

@gordonwang0
Copy link
Contributor

We have implemented a configurable auto-renewal of the device ID and EST identity certs.

The option is available here for device identity certs:

# [provisioning.attestation.identity_cert.auto_renew]
# threshold = "80%"
# retry = "4%"

And here for EST identity certs:

# [cert_issuance.est.identity_auto_renew]
# threshold = "80%"
# retry = "4%"

Note that this feature isn't released yet and will go in a future release. However, you can try it out now by downloading the latest packages from this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants