Working of IWA
- 21 Aug 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Working of IWA
- Updated on 21 Aug 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The following diagram indicates how the authentication procedure works:
- The user tries to access a CI-protected app.
- The app redirects the user to CI for authentication.
- The client browser recognizes that the server supports IWA and automatically sends the user's Windows credentials, such as the Windows username and password hash.
- With the hash received, the server looks up the user store and identifies the user.
- The server validates the credentials and creates a unique and encrypted challenge to send back to the client browser.
- This challenge can be only decrypted using the user's password which the browser already has with itself.
- The client browser decrypts the challenge with the user's credentials which the browser already knows and sends the response back to the server.
- The server checks whether the response for the challenge is correct and serves the user-requested resource if the answer is correct. If the answer is wrong, the server denies access to the requested resources and sends an unauthorized message.
- The server then grants access to the requested resource.
Was this article helpful?