Description of the idea
Add a field into Oauth2 client secret config to store the expiry date. And have this date used then in Messages.log for expiry alerting like ssl certs.
Who is the target audience?
Intersystems Administrators
What problem does it solve?
There is a risk of oauth stopping working for systems as there is no alert mechanism for expiry
How does this impact the efficiency, stability, reliability, etc, of the product?
Systems more reliable as Oauth already set up will alert when coming up to expiry and also when expired so more reliablie, conistent and working in line with ssl cert expiry
Provide a specific use case or scenario that illustrates how this idea could be used in practice.
On a rolling 1 year oauth credential add in date. 30 days from expiry it may alert like ssl (I would like this configurable and it not being the same level as the ssl warnings which i think should be less until a user configurable number of days to bring and then admins can request/update the oauths in a timely manner
Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!
