Which aspect of EPP are you submitting for?
Endpoint Protector Server
What is a one sentence summary of your feature request?
Display the validity status of predefined Offline Temporary Passwords in the existing Status column instead of always displaying N/A.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
The Offline Temporary Password list already contains two separate columns:
Status – Displays the validity of Custom Offline Temporary Passwords (for example, Active and Expired).
Revoke Status – Displays the lifecycle of the OTP (for example, OTP Generated, OTP Used, To be revoked, and Revoked Sent).
For OTPs created using the Predefined duration option, the Status column always displays N/A, regardless of whether the OTP is still redeemable or has expired.
This makes it difficult for administrators and Helpdesk staff to determine whether a predefined OTP is still valid. The Revoke Status column does not provide this information because it only shows the lifecycle of the OTP, not its validity.
Rather than introducing a new field, the simplest solution would be to extend the existing Status column to also indicate the validity of predefined Offline Temporary Passwords.
For example:
Active – The OTP is still redeemable.
Expired – The OTP is no longer redeemable.
The preferred solution is for the existing Status column to show Active or Expired for predefined OTPs. If a technical limitation prevents this, the expiry date and time could be displayed instead, so administrators can still determine whether the OTP remains redeemable.
This would provide a consistent experience between Custom and Predefined OTPs while improving usability and reducing confusion.
How do you currently solve the challenges you have by not having this feature?
Currently we have no way of determining from the management interface whether a predefined Offline Temporary Password is still redeemable or has already expired.
Our Helpdesk team must instead rely on knowing how the product behaves or ask the end user to attempt to redeem the OTP.
This creates unnecessary confusion because the Status column already reports validity for Custom OTPs but always displays N/A for Predefined OTPs.
Providing a meaningful status for both types of OTP would make administration more intuitive and reduce unnecessary support effort.
