#1
26th March 2016, 02:18 PM
| |||
| |||
IAS SQL Script
hii sir, I wants to know the key concepts of the Local IAS SQL Server logging ? will you please provide me the procedure of the IAS SQL Server logging ?
|
Similar Threads | ||||
Thread | ||||
KSLU Toppers Answer Script | ||||
VTU Answer Script | ||||
Anchoring script for MBA orientation |
#2
26th March 2016, 02:19 PM
| |||
| |||
Re: IAS SQL Script
As you asking for the key concepts of the Local IAS SQL Server logging here I am giving you key logging concepts that describe how a requests logged by IAS, IAS log file contents, and how IAS creates an XML document from accounting and authentication data. Data logged by IAS By default, IAS does not log any data until you configure it to do so. When you configure SQL Server logging, all required attributes, accounting, and authentication data that is normally logged in either IAS or database-compatible format is logged to the SQL Server 2000 or MSDE 2000 database. Initially, it is recommended that you enable the logging of accounting and user authentication requests. You can refine your logging settings after you determine your required data. Requests logged by IAS You can log the following information in a SQL Server database: Accounting-on requests, which are sent by the access server to indicate that it is online and ready to accept connections. Accounting-off requests, which are sent by the access server to indicate that it is going offline. Accounting-start requests, which are sent by the access server (after the user is authenticated and authorized by the IAS server) to indicate the start of a user session. Accounting-stop requests, which are sent by the access server to indicate the end of a user session. Authentication requests, which are sent by the access server on behalf of the connecting user. These entries in the log contain only incoming attributes. Authentication accepts and rejects, which are sent by IAS to the access server, indicating whether the user should be accepted or rejected. These entries contain only outgoing attributes. Example of the IAS configured for SQL Server logging using the XML file <Event> <Computer-Name data_type="1">MYNAS</Computer-Name> <Event-Source data_type="1">IAS</Event-Source> <Acct-Session-Id data_type="1">10</Acct-Session-Id> <NAS-IP-Address data_type="3">10.10.1.1</NAS-IP-Address> <Service-Type data_type="0">2</Service-Type> <Framed-Protocol data_type="0">1</Framed-Protocol> <NAS-Port data_type="0">7</NAS-Port> <NAS-Port-Type data_type="0">5</NAS-Port-Type> <Tunnel-Type data_type="0">1</Tunnel-Type> <Tunnel-Medium-Type data_type="0">1</Tunnel-Medium-Type> <Calling-Station-Id data_type="1">10.10.1.2</Calling-Station-Id> <Tunnel-Client-Endpt data_type="1">10.10.1.2</Tunnel-Client-Endpt> <User-Name data_type="1">MYDOMAIN\Administrator</User-Name> <Client-IP-Address data_type="3">10.10.1.1</Client-IP-Address> <Client-Vendor data_type="0">0</Client-Vendor> <Client-Friendly-Name data_type="1">MYNAS</Client-Friendly-Name> <MS-RAS-Vendor data_type="0">311</MS-RAS-Vendor> <MS-RAS-Version data_type="1">MSRASV5.20</MS-RAS-Version> <MS-RAS-Client-Version data_type="1">MSRASV5.20</MS-RAS-Client-Version> <MS-RAS-Client-Name data_type="1">MSRAS-0-MYCLIENT</MS-RAS-Client-Name> <Provider-Type data_type="0">1</Provider-Type> <Class data_type="1">311 1 192.168.0.123 02/20/2003 19:03:02 9</Class> <SAM-Account-Name data_type="1">MYDOMAIN\Administrator</SAM-Account-Name> <Fully-Qualified-User-Name data_type="1">MYDOMAIN\Administrator</Fully-Qualified-User-Name> <Authentication-Type data_type="0">4</Authentication-Type> <Packet-Type data_type="0">1</Packet-Type> <Reason-Code data_type="0">0</Reason-Code> </Event> |