After configuring IWA with SSL, users get a popup to enter domain credentials Skip to main content
https://support.okta.com/help/answers?id=906f0000000i0cjia0&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
JeremyAdmin WheelerAdminJeremyAdmin WheelerAdmin 

After configuring IWA with SSL, users get a popup to enter domain credentials

I can use IWA without SSL fine, users just need to confirm they want to go to the non-secure site.

Once I put in the SSL cert and configure everything to use HTTPS, the users now get a popup window where they need to enter their domain credentials. It seems this popup is coming from IIS. I followed the instructions provided by Okta for the SSL cert config with no luck.

Has anyone else run into this? This is using IIS on a 2012 server.
Asher RosenbergAsher Rosenberg
You may be running into the same issues we did, which were resolved with the 1.9.1 version of the IWA Client 
[We have improved the app sign-in experience for customers with Integrated Windows Authentication (IWA) in certain environments.]
This client is still in EA, and you will need to request a link from Support for that.
JeremyAdmin WheelerAdminJeremyAdmin WheelerAdmin
Thanks, I'll try that. I think I finally got the cert working because I show a secure connection. But now I get "Not Found, HTTP Error 404. The requested resource is not found". Not sure why it's such a chore to get IWA working.

I'll request version 1.91, hopefully that will help. Thank you for the reply.
Jason RielJason Riel
We had the same issue with the pop for credentials.  We had to create a group policy to add our domain suffix to the intranet sites list for Internet Explorer on all computers. After doing so users no longer got the pop up. 
Martijn BalinkMartijn Balink

I run into the exact same issue. I have a signed certificate installed on the IIS server.

http://server.domain.com/iwa/authenticated.aspx gives me a good result

https://server.domain.com/iwa/authenticated.aspx gives me a popup from my browser asking me for username and password. 

Users complain about the security message they get when okta redirects them back to the (insecure http) IWA application, so I need to get SSL up and running combined with iwa. I have just upgraded my agent to the latest public release (1.8.1) but to no effect.