About this file

SOO Attachment D

View the file

Other files

File Type Posted
Amend_4_Questions_and_AnswersAugust_30.docx DOCX document
Amend_3_Questions_and_AnswersAugust_27.docx DOCX document
QuestionsPosted15Aug13.docx DOCX document
Amendment001SOOPageChange.pdf PDF
SOO_Attachment_K_-_FSM_6600_Systems_Management_6680_Security_of_Info-InfoSystemsandInfoTechnology.doc DOC document
Amendment001RFPPageChanges.pdf PDF
SOO_Attachment_L_-_USDA_Web_Standards_and_Style_Guide.pdf PDF
Amendment_000002.pdf PDF
Amendment_001.pdf PDF
QuestionsPosted7Aug2013_(2).docx DOCX document
USDA_Web_Standards_and_Style_Guide_v1_1.pdf PDF
USDA_Incident_Mgmt_Policy.doc DOC document
FS_OSOH_WC_PreproposalConference_v01_20130802_PMO.pptx PPTX presentation
SOO_Attachment_G_FS_WC_OSOH_VendorDemoScenarios-27Jul13-POSTED.docx DOCX document
SOO_Attachment_F_Commonly_Used_Forms-27Jul13-POSTED.zip ZIP file
RFP_Attachment_6_Pricing_Tables_31Jul13-POSTED.xls XLS spreadsheet
SOO_Attachment_E_Current_Database_Field_Descriptions-27Jul13-POSTED.docx DOCX document
SOO_Attachment_J_USDA_DemographicsbyMission_Area_Agency_31Jul13-POSTED.docx DOCX document
RFP_Attachment_3_Past_Performance_Questionnaire-27Jul-POSTED.docx DOCX document
SOO_Attachment_I_OSOH_DepartmentRegulation(DR)4410-004_OHRM_DR30Jul13-POSTED.pdf PDF
RFP_Attachment_1_FS_WC_OSOH_SOO-31Jul13-POSTED.docx DOCX document
RFP_Attachment_2_QASP-30Jul13-POSTED.docx DOCX document
RFP_AG-7604-S-13-0033_SaaS_Reporting_Incidents-1August2013-POSTED.docx DOCX document
SOO_Attachment_H_WC_DepartmentRegulation(DR)4430-003_OPPM_DR30Jul13-POSTED.pdf PDF
RFP_Attachment_5_VPAT_Checklist-27Jul13-POSTED.doc DOC document
SOO_Attachment_B_FS_OSOH_WC_Business_Process_Standardization-27Jul13-POSTED.docx DOCX document
SOO_Attachment_C_FS_OSOH_WC_IntegratedProjectRequirements-31Jul13-POSTED.xlsx XLSX spreadsheet
RFP_Attachment_4_Client__Authorization_Letter_for_Past_Performance_Questionnaires-27Jul13-POSTED.doc DOC document
SOO_Attachment_A_Acronymns_used_in_Document-27Jul13-POSTED.docx DOCX document
Show all 29

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Solicitation: AG-7604-S-13-0033

Attachment D- SSO API SpecificationPage 1 of 2
Created on: 7/17/13Last Updated on: 7/17/13

Attachment D – SSO API Specification

Introduction The Forest Service (FS) utilizes, ConnectHR, an Employee self-service Web application that provides a mechanism for Employees to launch other web applications that require secure access without requiring Employees to re-enter user ID and password information.

This is done through the use of an Application Program Interface (API). ConnectHR uses standard Single Signon Server (SSS) API for launching third party Web applications. The SSS API utilizes industry standard technology (i.e., XML transactions over SSL) to ensure security integrity. All information transferred through the interface is for SSO security credentials only.

This document is intended to provide interested parties enough technical information to estimate the time required to implement the SSS API into an existing application without compromising the security of the API itself.

Overview An overview of the process by which an employee launches a 3rd party web application through ConnectHR is provided below.

Information transferred through the interface is for SSO security credentials only as illustrated in Step 6 above.

Attachment D- SSO API SpecificationPage 2 of 2
Created on: 7/17/13Last Updated on: 7/17/13

Example of SSS Transactions An example of the SSS XML transactions is given below.

Request:

<signon_employee request_id=” 100023” > <user_id>” 123456789” </user_id> <client_code>” 12345” </client_code> <pin>” 12345” </pin> <application>” OSHA” </application> </signon_employee>

Successful response:

<signon_employee request_id=” 100023” code=” 0000” msg=” ” > <token>2933bf8f-7b36-11d2-b20e-00c049f983e60</token> <last_signon date_time=” 2002-11-08T15:33:54Z” />

<identificication ssn=” 123456789”employee_id=” 123456789” />
<name first=” Smokey”middle=” T”last=” Bear” />

<division>abcdef</division> </signon_employee>

Error response:

<signon_employee request_id=” 100023” code=” 0001” msg=” Parse Error” > <token></token> <last_signon date_time=” ” />

<identificication ssn=” ”employee_id=” ” />
<name first=” ”middle=” ”last=” ” />

<division></division> </signon_employee> image2.png image1.png

File details come from the government source that posted it. Updated .