When testing before the standard login is shut off you may need to bypass which is such:
https://zone.taleo.net/smartorg/iam/accessmanagement/login.jsf?redirectionURI=https%3A%2F%2Fzone.taleo.net%2Fsmartorg%2FTaleoHomePage.jss&TARGET=https%3A%2F%2Fzone.taleo.net%2Fsmartorg%2FTaleoHomePage.jss
Oracle has announced that they are ending support for SHA-1 and migrating all it’s products to be SHA-2 compliant. Today they have released the information needed in order to accomplish this.
TCC-TCB SHA-2_CustomerDocument_Final is the Oracle white paper on the migration.
A shout out to Kelly Amott for bringing this to resolution. I’ve always wondered what the difference between the the requisition reopen and reactivate operations and there’s not a bunch in the documentation that I’ve seen that would explain it. He got the answer from a case and was kind enough to share.
Update and FYI – To take the req off hold I was using the Requisition – reopen spec. Oracle advised that reopen is for cancelled reqs. The specification I needed to be using is the Requisition – reactivate.
