Unexpected Authentication Prompts

 This article is suitable for an IT Adminstrator

Ref: 201407281240
Last Edited: July 28th, 2014


When attempting to open a process library webpage, a dialog box prompts for credentials.

Cause 1

If there's a prompt for credentials, it means the user account seeking access to files that comprise the webpage doesn't have sufficient permissions. Of course, this could be intended security behaviour. Otherwise, it would suggest incorrect permissions, perhaps even on a single file amongst many.

Solution 1

Check the permissions of the Triaster Server folder structure as described in this article.
'Triaster Server 2011 - Folder and File Permissions'

Cause 2

Authentication prompts have been known to result from a missing file. Why that should have caused a prompt for credentials isn't fully understood: it could be that a redirect to another file in response to a missing file is what raises the prompt, where there are insufficient permissions on the response file. However, that hasn't been confirmed.
A specific example is a reference within the generated Toolbar file to a script file that doesn't exist in the folder specified.
<script language="javascript" type="text/javascript" src="functions.js"></script>
According to that, 'functions.js' would be expected to be in:
but it isn't there. Although that spurious reference applies to every Toolbar, it doesn't result in a prompt for authentication on every system. That would reflect different authentication methods and permissions employed on different systems.


A browser's status bar may identify a missing file. More generally, Fiddler is a tool that has been found to be useful when investigating authentication issues.
It can be installed on a client PC, and used to monitor web requests.
This is a typical record when opening a process library webpage that includes the Toolbar.
Checking the associated folder confirms the file doesn't exist.

Solution 2

Usually, the remedy would be to ensure the required file is in the expected place. In this example case, 'functions.js' is actually redundant. Indeed, if it were copied to the expected location, it would corrupt the appearance of the Toolbar. However, particularly as the Toolbar page is generated, and therefore not editable, the file request needs to be fulfilled to avoid the error. The solution is to create an empty 'functions.js' file in the expected location.


Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on + 44 (0)870 402 1234.
Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk