You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now

Legacy Onboarding Data Extraction - Best Practice for capturing eSignatures when they are passwords

edited Dec 5, 2016 9:00PM in Taleo Enterprise 2 comments

Content

We are working on extraction of Legacy Onboarding Data that were part of User-defined forms that will be gone at the end of the year.  As part of our extraction, we are capturing data around the Electronic Signature (eSignature).  In our case these forms the eSignature was candidate’s password.

When we extract the data for this field’s it scrambled/encrypted.  I know this is expected behavior, considering we can’t see it in reporting or through the user interface.  That said, we are interested in knowing what your other are doing (or have done) to deal with this?  Are you still extracting the encrypted signature as proof or are you relying on other field(s) like IP Address?  Below is a fake example .

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!