Jump to content

Internet Authentication Service

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by NightmareWolf54k (talk | contribs) at 10:29, 10 December 2020 (Overview). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Internet Authentication Service (IAS) is a component of Windows Server operating systems that provides centralized user authentication, authorization and accounting.

This is very important news to have in life so that is why this is not a lie

Logging

By default, IAS logs to local files (%systemroot%\LogFiles\IAS\*) though it can be configured to log to SQL as well (or in place of).

When logging to SQL, IAS appears to wrap the data into XML, then calls the stored procedure report_event, passing the XML data as text... the stored procedure can then unwrap the XML and save data as desired by the user.

History

The initial version of Internet Authentication Service was included with the Windows NT 4.0 Option Pack.

Windows 2000 Server's implementation added support for more intelligent resolution of user names that are part of a Windows Server domain, support for UTF-8 logging, and improved security.[1] It also added support for EAP Authentication for IEEE 802.1x networks. Later on it added PEAP (with service Pack 4).

Windows Server 2003's implementation introduces support for logging to a Microsoft SQL Server database, cross-forest authentication (for Active Directory user accounts in other Forests that the IAS server's Forest has a cross-forest trust relationship with, not to be confused with Domain trust which has been a feature in IAS since NT4), support for IEEE 802.1X port-based authentication, and other features.[2]

All versions of IAS support multi domain setups. Only Windows Server 2003 supports cross forest. While NT4 version includes a Radius Proxy, Windows 2000 didn't have such a feature. Windows Server 2003 reintroduced the feature and is capable of intelligently proxy, load balance, and tolerate faults from faulty or unreachable back-end servers.

References