This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 23%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
I'm currently experiencing issues with the AuthPersistSingleRequest attribute. I'm currently attempting to use it in an XML file linked to our IIS Auth Portal but whenever I attempt this, it flags as the configuration file is not well-formed XML. Attached error and XML config. Has anyone else experienced this? I've also tried to set it in the following files to no avail:
C:\Windows\System32\inetsrv\Config\Schema\IIS_schema.xml
C:\Windows\System32\inetsrv\Config\applicationHost.config
I've also tried variations of the line:
<authPersistSingleRequest="true">
<authPersistSingleRequest="true" />
<authPersistSingleRequest enabled="true" />
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 24%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
You can try to deal with this situation is to go step by step and comment out certain sections of xml and applicationHost.config file and check for application behavior.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
You are treating it like an element, it is an attribute. Refer to the docs here. It is an attribute of the windowsAuthentication element.
<security>
<authentication>
<windowsAuthentication authPersistSingleRequest="true" />
</authentication>
</security>
Thank you, that appears to have accepted it now, I also had to amend the overrideModeDefault values in the applicationHost.config file to get it to work afterwards. However I'm still having the initial error where the credentials are being cached and re-used by IIS rather than getting it to re-prompt. Any ideas?
I cannot answer to that as I'm not sure what problem you're having. If you're using Win auth then reauthenticating each time a request is made seems wasteful of resources. A Win token is cached by Windows at login of the user. So continually reauthenticating on an IIS request is going to simply do the same work every time.
I suspect the issue may be with whatever framework you're using for your web app. For example ASP.NET is going to back things by session. Once it has a valid auth token I don't believe it would bother reauthenticating again until the session expires. This is at a higher level then IIS uses. But I've never tried to do what you're doing to verify.
Thanks Michael, our issue is that if an iPad for instance is using IIS alongside a filtering system, it prompts for user credentials upon initial use of the browser. We set an expiry in the filtering system of, for example, 40 minutes. However, the browser doesn't re-prompt for these credentials again after this expiry is hit and only does this when the browsing tabs and all browsing windows are closed and re-opened. Is there a way in which we could set a trigger for IIS to re-request authentication outside of use of this filtering system?
What type of app are you hosting in IIS that uses Windows auth (e.g. NET Framework, NET Core, etc)?