-
Notifications
You must be signed in to change notification settings - Fork 617
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
Add parameter to vault token renewal #274
Comments
Sure. Was expecting that this would happen at some time. |
Add the 'renewtoken' option for vault certificate sources to make the token renew interval configurable. Fixes #274
Add the 'renewtoken' option for vault certificate sources to make the token renew interval configurable. Fixes #274
@deuch I've pushed a change that should make the token renew interval configurable. You have to set the |
Hello, I've made the test and it doesn't seem to work, fabio doesn't want to start, telling me that the port is already used ... Stop fabio, kill every instance, check with netstat (root) and nothing is listening on that port. Revert back to 1.4.3 and it works fine (with exact same properties file) ... Please find the logs :
|
@deuch Hmm, I could check whether the Can you try with a different port or wait a bit? I think 2 min is the timeout. I just want to confirm that the vault change works. |
I try an another port, and no need to wait, the fabio process is immediatly killed with the fatal error. Please find the commands i use to show you the issue. I've started with the issue-274 branch and just after with the 1.4.3. You will see that the 1.4.3 works fine on the same server with the same config (i've just changed the symbolink link for the fabio binary).
|
Find something with the proxy address : If i put 2 listeners in proxy.addr fabio fails to start ...
With this config it works with your patch (only 1 listener):
|
That looks strange. I'll have a look. |
also fails like this
I'll open another ticket. Thanks for finding this. |
I've opened #279 and found the issue. |
Add the 'renewtoken' option for vault certificate sources to make the token renew interval configurable. Fixes #274
I've fixed #279 and rebased the patch. Could you please try again? |
Hi, i've made some test and i think it doesn't work as expected. In fact, the renewSelf function is called in the load function (vault_source.go) each time you want to refresh the certificates list. proxy.cs=cs=ssl-vault;type=vault;cert=secret/fabiodemo-001/certs;renewtoken=7m;refresh=1m But at the end, the token is renew every minutes :
|
Any update on this topic ? |
Renewing the token before further API calls are made is fine. Setting renewtoken=7m just ensures that the token is valid for at least another 7 minutes before the certificates are looked up. If the token's TTL is longer than that, nothing happens. What did you expect to happen instead? |
I want to decorelate the certificate renew and the token renewal. I can set the renewal token to 20mn for example and certificate every 1mn. But in the current implementation, the token is refreshed everytime the certificates are updated. So the Vault logs are flooded by token renewal. And i do not need to to refresh every minute ... So i would like to have those parameters working as expected. |
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Don't attempt Vault token renewals if the token isn't renewable. If it is, don't renew the token with each refresh; only do so if the token would expire shortly. Increase the token's lifetime by its original TTL.
Fabio need to have a parameter in the fabio.properties to let the user set the renewal interval for the Vault Token. It's 1h actually and it's too long :-) We've issue because our tokens have a 20mn lease.
The text was updated successfully, but these errors were encountered: