Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
Knowledge Partner
Knowledge Partner
55 views

How to disable only eSignature functionality for a user in case of 3 back to back eSignature failure

In our organization, for one of the GxP templates, design was done in such a way that if there is "eSign" custom group assigned to user ,that user will be able to provide eSignature as a reviewer or approver to the artifacts such as test script, test set etc.

User credentials are LDAP authenticated in ALM application.

In a particular case, user's "eSign" functionality should be disabled or removed if the user makes 3 back to back e-sign failure due to entry of wrong credentials. ( 3 wrong login attempts). Here requirement is to just disable the eSign functionality by sending a mail to user that it got disabled due to his/her 3 back to back wrong attempts, user should remain active in alm application and project and should be able to perform all other functionalities except eSign.

Could some one please guide on how approach this requirement and how to design the logic.

What are all the ALM tables and OTA API objects ,methods and interfaces which can used in handling this requirement.

Regards,Srihari
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.