01.02.2014 Views

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

TABLE OF CONTENTS - Department of Public Social Services

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Los Angeles COUNTY<br />

<strong>Department</strong> <strong>of</strong> <strong>Public</strong> <strong>Social</strong> <strong>Services</strong><br />

LEADER Replacement System (LRS)<br />

6238<br />

6239<br />

6240<br />

6241<br />

6242<br />

6243<br />

6244<br />

6245<br />

6246<br />

6247<br />

6248<br />

6249<br />

6250<br />

6251<br />

6252<br />

6253<br />

6254<br />

6255<br />

6256<br />

6257<br />

6258<br />

6259<br />

6260<br />

6261<br />

6262<br />

6263<br />

6264<br />

6265<br />

6266<br />

6267<br />

6268<br />

6269<br />

6270<br />

6271<br />

6272<br />

37. The LRS shall allow for both CSOs and LSOs the ability to<br />

enable and disable existing individual COUNTY-specified<br />

User IDs.<br />

38. The LRS shall allow for both CSOs and LSOs the ability to<br />

enable and disable one or more groups <strong>of</strong> existing COUNTYspecified<br />

User IDs.<br />

3.4.1.2. Session Management.<br />

Session management is the process <strong>of</strong> keeping track <strong>of</strong> User<br />

activity across one or more sessions <strong>of</strong> interaction with the LRS.<br />

LRS session management shall keep track <strong>of</strong> which services or<br />

functions have been invoked by a User and the state <strong>of</strong> the LRS<br />

Data which the function or service is accessing, so that the same<br />

state may be restored if the User terminates a current session and<br />

initiates a new session at a later time.<br />

1. The LRS shall track the User’s session from the time that the<br />

User is authenticated to the LRS to when the session is<br />

terminated, either explicitly by the User or implicitly through<br />

a specified event such as accidental loss <strong>of</strong> connectivity,<br />

designated period <strong>of</strong> inactivity, or closure <strong>of</strong> the main Web<br />

browser window.<br />

2. The LRS shall allow only one session per User to be active at<br />

any one time.<br />

3. The LRS shall include a means to identify all interactions<br />

related to a single User session in such a manner that<br />

prevents LRS compromise.<br />

4. The LRS shall allow either the User agent (e.g., the Web<br />

browser) or the LRS technical infrastructure (e.g., the Web<br />

server) to terminate a session.<br />

5. The LRS shall require that the User re-authenticate when a<br />

session is terminated.<br />

6. The LRS shall not cache any User credentials for future use<br />

(i.e., display <strong>of</strong> a User ID after termination <strong>of</strong> current session<br />

for use in starting a new session).<br />

7. The LRS shall terminate a session in the event <strong>of</strong> any<br />

System/network failure.<br />

LRS RFP - Attachment B (SOR) Page 178 November 30, 2007

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!