Symptoms
This is regarding SQLUM behind a DMZ functionality in SmartForms Runtime site.
For more info, use this link: http://help.k2.com/kb001357
Diagnoses
See resolution
Resolution
In conclusion, regarding getting SQLUM functionality to work behind a DMZ, you need to make sure of the following:
Please follow KB001357 - http://help.k2.com/kb001357
Also, please follow this article: http://help.k2.com/onlinehelp/k2smartforms/ICG/current/default.htm_Configure_SmartForms_for_SQLUM/K2_Multi-Auth_-_Configure_SmartForms_for_SQL_Server_User_Manger__SQLUM_.htm
It comes down to two things that should optionally be implemented, but both would probably be a good idea:
1) The local Application Pool account on the DMZ server for the SmartForms runtime site should also be created as a local user on the K2 server (behind the DMZ) with the same rights. Since this account is not an AD account, it will have to be local.
2) Please also enter the DMZ server hostname into the AuthInit field in the K2 Database:
On the SQL Machine run the following query:
UPDATE TK2].2HostServer].rSecurityLabel]
SET AuthInit =
'
DENALLIX
MACHINE_NAME]
'
WHERE RSecurityLabelName] = 'K2'
Where rMACHINE_NAME] is the K2 Server Machine name, also remember to keep the list of configured domains.
As per KB001357 we currently have the following workarounds that we have tested:
• Setting the K2SQL Label as default label
• Adding the K2 Server Machine Name as a domain in the AuthInit column
