SOO_Attachment_D_SSO_API_specification-27Jul13-POSTED.docx
DOCX document 118 KB Posted
- Solicitation number
- AG-7604-S-13-0033
About this file
SOO Attachment D
View the file
Other files
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 Specification | Page 1 of 2 |
| Created on: 7/17/13 | Last 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 Specification | Page 2 of 2 |
| Created on: 7/17/13 | Last 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 .