Hello there!

Need Help? We are right here!

Support Icon
miniOrange Email Support
success

Thanks for your Enquiry. Our team will soon reach out to you.

If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com

Search Results:

×

Integrated Windows Authentication (IWA)

IWA solution adds an extra layer of security and convenience for organizational users by allowing simple domain-joined SSO flow while accessing multiple resources with their existing Windows credentials.

  Eliminates the need for multiple login prompts.

  Supports Kerberos and NTLM protocols.

  Effective in intranet environments with Active Directory.

  Secures credential storage and transmission.

Book a Demo Setup Guide
Integrated Windows Authentication (IWA)

What is Integrated Windows Authentication (IWA)?

Integrated Windows Authentication (IWA authentication), introduced by Microsoft for Windows NT-based systems, simplifies user login to web applications by using Windows Active Directory as the user store. It is a popular choice among Windows server users and administrators.

It leverages protocols like Kerberos and NTLM. Kerberos uses tickets to allow nodes to prove their identity securely, while NTLM is a challenge-response authentication protocol. Both protocols are essential for enabling seamless and secure access to resources within a Windows environment.



Empowering 25K+ Customers Globally

How Does Integrated Windows Authentication Work?

This workflow integrates Windows authentication with SAML to provide seamless Single Sign-On (SSO) for users accessing various applications. The Identity Broker and IWA modules work together to authenticate users against the Active Directory using Kerberos, enabling secure and efficient access management. This IIS server authentication leverages connectors for logging into custom-designed proprietary apps.

1. User Access Attempt

The user on a domain-joined machine tries to access their configured application (SAML Application, .NET Application, or Custom Application).

2. Authentication Request

The configured application sends an authentication request to the miniOrange Identity Broker via a connector (if required). miniOrange sends a SAML request to the IWA module hosted on the IIS server.

3. Kerberos Authentication

The IIS server retrieves the user's information via Kerberos authentication from the Active Directory (AD).

4. User Verification

The IWA module verifies the user's information with the Active Directory.

5. SAML Authentication Response

The IWA module sends a SAML authentication response back to the Identity Broker. The user is redirected to their application's homepage, successfully authenticated.

Integrated Windows Authentication: miniOrange IWA Module

IWA Use Cases

Corporate Intranets

Enterprise Applications

Legacy Applications

Remote Access

Corporate Intranets

Employees accessing internal company websites or applications without repeatedly entering their login credentials.

Enterprise Applications

Integrated into cloud apps and Onpremise applications that require secure and seamless user authentication within a Windows environment.

Legacy Applications

Seamless integration with Legacy applications e.g. Oracle E-business Suite and SAP ECC.


Know More

Remote Access

Users accessing network resources via VPN or remote desktop services.


Know More

Features of Windows Integrated Authentication for Enterprises

Single Sign-On (SSO)

IWA enables Single Sign-On, allowing users to log in once and gain access to multiple resources without needing to re-enter credentials.

Security

It uses the underlying Windows security mechanisms, such as Kerberos or NTLM (NT LAN Manager), to authenticate users, providing a secure way to manage authentication.

User Experience

Users experience seamless access to resources, as the authentication process happens in the background using their existing Windows session credentials.

Ease of Administration

Administrators can manage user accounts and access policies centrally through Active Directory, simplifying the management of user authentication and permissions.

Integrated Windows Authentication (IWA): Use cases


IWA Services
Pricing


Request a Quote
  • Flexible pricing based on your user tiers, with volume discounts available.
  • Instant customized quotes that fit your budget and requirements.
  • Expert guidance on the best solution for you.
  • Affordable pricing options for large enterprises, government agencies, and SMBs.

*Please contact us to get volume discounts for higher user tiers.



Frequently Asked Questions


What is the difference between integrated Windows Authentication & Basic Authentication?

Feature Integrated Windows Authentication Basic Authentication
Credential Transmission Not sent in plain text Sent in plain text (Base64)
Security More secure (Kerberos/NTLM) Less secure (vulnerable without SSL)
User Experience Seamless, automatic login Requires manual entry
Best Use Case Intranet environments Intranet and internet applications
Requirement Domain membership No domain requirement

What is the meaning of Windows Authentication?

Windows authentication (formerly named NTLM, and also referred to as Windows NT Challenge/Response authentication) is a secure form of authentication because the user name and password are hashed before being sent across the network.

Which browser versions are supported by Integrated Windows Authentication (IWA)?

Integrated Windows Authentication is compatible with most modern web browsers but may have limitations with some HTTP proxy servers. It is ideal for intranets where all clients are within a single domain. Supported browsers include:

  • Internet Explorer 2 and later
  • Mozilla Firefox
  • Opera 9.01 and later
  • Google Chrome
  • Safari
  • Microsoft Edge 77 and later

What are Pros and Cons of IWA

The key advantage of IWA authentication is that users logged into the Windows domain are automatically authenticated for IWA-enabled web apps without needing to re-enter credentials, provided they are valid users and the main drawback of IWA authentication is its reliance on Windows Active Directory, requiring both the client and server to run Windows NT-based systems and be connected to the server's domain. It is limited to intranet environments.

   '

x

*
*



*






 Thank you for your response. We will get back to you soon.

Please enter you work email-id

Want To Schedule A Demo?

Request a Demo
  



Our Other Identity & Access Management Products