My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2009-171
San-Marcos
>
City Clerk
>
03 Resolutions
>
2000 s
>
2009
>
Res 2009-171
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/15/2010 9:35:16 AM
Creation date
12/23/2009 8:30:54 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
2009-171
Date
12/16/2009
Volume Book
184
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
71
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
brazos <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />124 Security Administrators should be The session timeout period is set via the web.config file on Expected <br /> able to define the duration the server. <br /> of inactivity before a <br /> session terminates. <br />125 Security Administrators should be Administrators can not only create an expiration date for Expected <br /> able to create user IDs with each user, but they can also create a beginning date for <br /> an expiration date and each user if they don't want access to be granted until <br /> time. sometime in the future <br /> <br />126 <br />Security <br />Administrators should be . <br />The same discussion above related to the security of users <br />Expected <br /> able to create security also applies to groups. Each group is also assigned a <br /> profiles to establish security level and users can be assigned multiple groups <br /> <br />individual and group . <br /> privileges. <br />127 Security Administrators should have Currently the system allows Administrators to see how many Desired <br /> the ability to monitor (in real and who is logged into the system. We can provide <br /> time) and report on file immediate audit reports as to what was changed but would <br /> access activities for a also be willing to identify what action was last taken by each <br /> particular user, group, user. For example, Mike logged in at 9:20am and last <br /> application, device, and file. accessed the Citation Entry Screen. <br />128 Security The System should display We currently display the security level of each user at the top Desired <br /> a configurable security of the screen when they login. If the City desires specific <br /> banner upon login. wording at the top of every screen, we can provide that <br /> capability at no additional cost. <br />129 Security To ensure the security and Based upon the security roles assigned to each user <br />they Desired <br /> integrity of data, access , <br />access the DBMS based upon pre-built security roles that <br /> should be controlled further assure data control and integrity. <br /> t hrough the user's security <br /> profile.
The URL can be used to link to this page
Your browser does not support the video tag.