
e5278 (e5278) asked a question.
Trying to deploy a new OKTA AD Agent node. After entering in tenant name information, "Sign into OKTA with Administrative User Account" window is mostly blank, with no options to authenticate, thus we cannot complete Agent deployment/installation.

can you enable TLS and try
TLS is enabled. Still same issue. Any additional configs?
By chance, do you have a custom Okta domain? I have had a few customers run into this issue. Make sure the server has access, using Internet Explorer, to your Okta login page to confirm access. You may have to double check - possibly an internal DNS - to whitelist your custom Okta domain. Otherwise, depending on your access to DNS and if you have a relatively new org, you could roll back the custom domain setup, install the AD Agents, and run thru the custom URL steps again.
I see the same issue too, Any Luck >?
I am running into the same issue. I have a new domain up and running, and ensured TLS is enabled. Default browser is IE, and confirmed it can reach our Okta sign-in page (<domain>.okta.com). Had to put a few websites in the trusted sites list to get it fully load. Can sign in no issue.
Agent installer shows the same blank screen as represented by the previous post's screenshots. Can't seem to find any additional changes to make to allow the sign-in screen to show up.
Anyone find a solution that worked for them?
Update (Resolution): I got Okta Support involved and they advised me on setting up a website "trace" for all web activity during the install process to determine why the window was blank. The trace ended up showing me that the window was not going to our traditional sign-on link of <domain>.okta.com, but trying to go to our domain link, of okta.<domain>.com, which was not loading. Because it was routing to a domain address which doesn't exist, it simply stalls. The FQDN was really needed to point to an external web server. Popped the external web IP as an A-Record in the DNS, then using IE, ensured that the site would load (had to add a few URL's to the Trusted Sites as they popped up being blocked on loading). Once these steps were taken and IE would load up the login screen at okta.<domain>.com, reran the installer of the Agent and it successfully loaded the sign-in screen for Okta and I was able to complete the install.