Skip to main content


 

Symptoms


We have a Single Sign-On (Windows Authentication) issue on our K2 Production environment. Whenever any user attempts to open a K2 Smartform, he is asked to enter his Network credentials.

We have done multiple attempts at analyzing the issue and have found the following remarks. Please use this information for your reference:

FYI:
Our production environment's hostname is XXXK2FE01
Our test environment's hostname is XXXMOSSK2T01

1. The issue most likely seems to be related to the "/identity/sts/windows" application in the IIS. It seems that whenever any user tries to open a K2 Smartform, it first redirects them to the STS/Windows application for authentication. HOWEVER, it is currently redirecting them to the FQDN URL https://XXXk2fe01.bah.bapco.int/identity/sts/windows. It SHOULD NOT redirect to the FQDN URL, it should redirect to the normal URL https://XXXk2fe01/identity/sts/windows

2. Generally in our network environment, we have a problem in Windows Authentication in all our servers when the URL has the FQDN in it.

3. We believe the solution is to somehow configure the server to use the non-FQDN url to perform the windows authentication step: https://XXXk2fe01/identity/sts/windows

4. On our K2 test server we do not have this issue at all. It seems to redirect to the correct url: https://XXXmossk2t01/identity/sts/windows
 

Diagnoses


Url to be added to lOCAL INTRANET ZONE
 

Resolution

Resolution:
"
Are the URLs added to the local intranet zone?
kindly see this:
http://help.k2.com/onlinehelp/k2smartforms/userguide/1.0.6/default.htm_Internet_Explorer _Settings.html?TocPath=Installation and Configuration|Post Install|_____4

https://www.k2.com/onlinehelp/k2blackpearl/userguide/4.6.7/webframe.html_troubleshooting_settingsforie.html
"




 
Be the first to reply!

Reply