LOTW certificate expiry reminder?

[timkirby]

I wondered why my recent QSOs hadn’t been uploaded to LOTW. Well, the reason was simple, my certificate had expired.

Because Cloudlog is so good at uploading records, it’s easy to miss that a certificate is expiring. As Cloudlog knows the date a certificate is expiring, could there be a warning if the date is getting close?

[magicbug]

Reasonable suggestion, 30 days?

[magicbug]

Then at 5 days show a constant reminder on the dashboard when you login

[timkirby]

Sounds great. Maybe could be in the banner at the top of the dashboard where it says ‘you have had x QSOs today’? Append a warning like ‘check for expiring LOTW certificates’ or similar?On 22 Dec 2022, at 22:28, Peter Goodhall ***@***.***> wrote: Reasonable suggestion, 30 days? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[timkirby]

That would work too!On 22 Dec 2022, at 22:30, Peter Goodhall ***@***.***> wrote: Then at 5 days show a constant reminder on the dashboard when you login —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[phl0]

I started some work and added a warning notifier to the LotW certs that shows an orange icon 10 days before expiry.

Code is here: https://github.com/phl0/Cloudlog/tree/lotwWarning

Will also add a notification to the dashboard.

[timkirby]

That looks great, Flo - thank you for the speedy response!

…

On 23 Dec 2022, at 09:56, Florian (DF2ET) ***@***.***> wrote: I started some work and added a warning notifier to the LotW certs that shows an orange icon 10 days before expiry. <https://user-images.githubusercontent.com/7112907/209314626-de05b5b5-e7f7-400c-89a5-ee6c65c082cd.png> Code is here: https://github.com/phl0/Cloudlog/tree/lotwWarning <https://github.com/phl0/Cloudlog/tree/lotwWarning> Will also add a notification to the dashboard. — Reply to this email directly, view it on GitHub <#1860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAHGW3OETSIAIBVNMRQDETWOVZOVANCNFSM6AAAAAATHFNUNI>. You are receiving this because you authored the thread.

[phl0]

That looks great, Flo - thank you for the speedy response!

No worries. This is not what you wished for but as I was at it discovering (again) how the code works here I thought this might also be helpful. Guess I will also make the 10 day more like 30. Opinions?

[timkirby]

30 is probably good. It looks like ARRL may take 3-4 business days to respond - so it’s definitely better not to leave it to the wire!

…

On 23 Dec 2022, at 10:25, Florian (DF2ET) ***@***.***> wrote: That looks great, Flo - thank you for the speedy response! No worries. This is not what you wished for but as I was at it discovering (again) how the code works here I thought this might also be helpful. Guess I will also make the 10 day more like 30. Opinions? — Reply to this email directly, view it on GitHub <#1860 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAHGW7I2CJNJOWX6GWEDPTWOV4ZJANCNFSM6AAAAAATHFNUNI>. You are receiving this because you authored the thread.

[phl0]

So my patch is complete now. It checks for expired certificates as well as certificates expiring in the next 30 days:

Are you able to test this?

[timkirby]

Excellent! I don’t know whether Pete is able to push the code change to my hosted instance. I’ve got my replacement certificate, but I can hold of installing it until I’ve tested it.

…

On 23 Dec 2022, at 13:58, Florian (DF2ET) ***@***.***> wrote: So my patch is complete now. It checks for expired certificates as well as certificates expiring in the next 30 days: <https://user-images.githubusercontent.com/7112907/209347683-9979aa4b-de84-4887-be97-1fe298629846.png> Are you able to test this? — Reply to this email directly, view it on GitHub <#1860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAHGW4QR4VDQD2UYIKSCTLWOWVYRANCNFSM6AAAAAATHFNUNI>. You are receiving this because you authored the thread.

[phl0]

Ah then you are on master branch most probably. This goes to dev first. So I may ask @magicbug or @AndreasK79 for a review before merging it :)

[timkirby]

Yes, I’m almost certainly on the master branch! Thanks again, Flo!

…

On 23 Dec 2022, at 14:16, Florian (DF2ET) ***@***.***> wrote: Ah then you are on master branch most probably. This goes to dev first. So I may ask @magicbug <https://github.com/magicbug> or @AndreasK79 <https://github.com/AndreasK79> for a review before merging it :) — Reply to this email directly, view it on GitHub <#1860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAHGW2ALO73L6E3DIPEER3WOWX3PANCNFSM6AAAAAATHFNUNI>. You are receiving this because you authored the thread.