config: added a configurable option for the expiration time of a JWT token

[mssola]

See the issue #510

Signed-off-by: Miquel Sabaté Solà msabate@suse.com

[flavio]

This seems to be used only when there's no jwt_expiration_time value configured inside of the config.yml. That should not happen right?
Also this is used when the value is something wrong; in that case I would just let everything crash. That would make the issue evident.

[flavio]

LGTM, I not 100% convinced about having the default expiration time defined also inside of the jwt class.

[mssola]

@flavio agreed. I just changed that.

[EugenMayer]

Did has been tested @mssola ? I do export this ENV var

"PORTUS_REGISTRY_JWT_EXIRATION_TIME": "100"

but i still get a timeout after 5 minutes. Any clues? I introduced this setting in the rancher catalog questions https://github.com/EugenMayer/docker-rancher-extra-catalogs/blob/master/templates/registry-slim/17/docker-compose.yml#L43

[mssola]

@EugenMayer works for me if I use: PORTUS_REGISTRY_JWT_EXPIRATION_TIME_VALUE

[EugenMayer]

@mssola why suddenly the _VALUE suffix? most of the variable do not need it? is it special

[mssola]

The REGISTRY part is because of what's explained here. As for the VALUE, at least on 2.0.x releases it was already there. Maybe we could've provided this specific value directly without adding a value key ? This is something that we can certainly simplify in next releases, because right now options like machine_fqdn and registry.catalog_page also have it and it feels redundant.