The Help contains information on how to build optimal career sections.
When a Career Section is created, a URL is automatically generated for the Career Section. When candidates access the Career Section of an organization, they are taken to the URL created for the Career Section.
The Personalized Job List - Matching Criteria feature enables system administrators to set the criteria that determine when a match is to be made between a job and a candidate. Only jobs that meet all specified criteria are displayed in the Career Section Jobs Matching My Profile page.
On the My Submissions page, the display of the job status can be configured to display whether submissions are still being accepted.
Job Submission Status is a feature that allows candidates to be informed of where they are in the hiring process because they can view the status associated to their job applications.
The Matched Candidate Display feature allows system administrators to specify if jobs manually matched to candidates in the Recruiting Center are displayed in the candidate's Career Section My Submissions page.
The system can be configured to send a request to the agent to confirm a candidate’s availability.
Customers who wish to have increased control over the information sent to Career Section users via email may choose to enable the Secure Message Delivery feature. When enabled, all messages are delivered to a secure Message Center accessible from any of the customer's Career Sections. Message recipients are directed to the Message Center to retrieve their messages.
Candidates can use the search functionality to find jobs via the Basic Search and the Advanced Search pages of a Career Section.
The Help panel displays helpful information to the candidate.
Single Sign-On (SSO) enables users to log into Oracle Taleo Enterprise Edition applications using their corporate credentials.
Single Sign-On (SSO) in Oracle Taleo Enterprise Edition is accomplished through the use of SAML (version 2.0). SAML provides a mechanism to exchange authentication and authorization data between two trusting entities.
SSO is set up by exchanging metadata files between the Identity Provider (IdP) and the Service Provider (SP).
There are two types of Single Sign-On flows: Identity Provider (IdP)-initiated and Service Provider (SP)-initiated.
Challenge, Error and Exit URLs can be defined to configure the destination to which the user will be redirected under various conditions.
A trust relationship is established between the IdP and the SP when both exchange their respective certificates.
The customer must configure synchronization of users between the Identity Provider(s) and Oracle Taleo Enterprise Edition.
Identity provider bindings specify the IdP URLs that can be used to perform various SAML transactions.
Trusted certificates are needed to confirm the identity of Identity Providers. Each assertion received will be validated against these certificates.
The Single Sign-On wizard enables internal candidates to link a candidate account to their SSO user identifier.
This is an example of an IdP metadata file.
This is an example of a metadata file for SmartOrg.
This is an example of a metadata file for Career Section.
Scripting on this page enhances content navigation, but does not change the content in any way.