[#85] Allow to customize secret expiry

[Luzifer]

[mshedsilegx]

This looks really good.
1- Can you think of a way to make the expiry list values customizable in "customize.yaml" ?
2- Can we display the date/time in UTC/GMT, to make sure it will not depend of the current TZ of the server ?

[Luzifer]

1- Can you think of a way to make the expiry list values customizable in "customize.yaml" ?

I could do some logic to derive the translation strings to be used from the seconds values and then it would be possible to specify them… 🤔

2- Can we display the date/time in UTC/GMT, to make sure it will not depend of the current TZ of the server ?

Indeed the time is displayed in browser local time… The API passes UTC to the browser.

[mshedsilegx]

OK, maybe I am not clear what the list of values would be in the drop down. Can we specify a number and a unit ?
examples:
30 mn
1 Hour
2 days

with a max value enforced at startup.

[Luzifer]

OK, maybe I am not clear what the list of values would be in the drop down. Can we specify a number and a unit ?

Yeah I did get what your intention was. Have a look at the README changes in the last commit…

[mshedsilegx]

I see, yes, that looks fine

[mshedsilegx]

I just tested, this is outstanding. Could you please document how would we access that custom expiration when creating the secret via automation - ie curl call to OTS API ? Many thanks.

[Luzifer]

Could you please document how would we access that custom expiration when creating the secret via automation

That has been added to the API documentation: operation/createSecret - i.e.

curl 'https://ots.fyi/api/create?expire=300' \
  -H 'content-type: application/json' \
  --data-raw '{"secret":"U2FsdGVkX1+w3BJhbu6nQiKOK6HI0ZRUvwWGQ066F8Q="}'

{
    "success": true,
    "expires_at": "2023-06-26T22:24:02.051952626Z",
    "secret_id": "1a40aec3-24df-4fe8-91f1-5788420797b7"
}