This week we have a post about troubleshooting custom login forms for an authentication channel. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied.
|Authentication Channel: Custom Login Page Failing with 500 Error
|The customer recently deployed an authentication channel with associated login page and error pages for their new application. They were unable to get the login pages to authenticate users after several attempts. Users attempting to authenticate received an HTTP 500 error in the browser.
|The customer was able to determine that none of the new web servers in the authentication channel worked and that it was not a result of the high availability configuration. We had the customer provide the web agent logs and a copy of their login page. Since this was a new web agent installation, we initially thought that the web agent was misconfigured but that did not turn out to be the case. The agent was properly configured for the web server and the application, but we did see several “HLA: Missing resource data” errors in the log.
|Customer copied the login.fcc from an existing authentication channel.
|The customer copied the login.fcc from the original authentication channel and failed to update it appropriately. The existing login.fcc used a static agent name which did not match the new agent configuration. Additionally, the new login page was not posting the target correctly to the login.fcc.
|We had the customer update the static agent name in the login.fcc to match the agent name used for the new web server. Additionally, the new login page was modified to include “-SM-” prior to “https://” for the target value that would be posted to the login.fcc. After the modifications were made, the new authentication channel worked as expected.
As always, we hope that you have found this information useful. If you need IAM assistance, reach out to SIS today and we would be happy to assist you. And subscribe to our newsletter to be notified about the posting of future articles and other SIS news.