SecureAuth IdP Version Affected: All
Description:
When users enter their credentials in an embedded browser for authentication, the following script error message appears: An error has occurred in the script on this page: "WebForm_DoPostBackWithOptions' is undefined"
Cause:
ASP.NET does not know that the embedded browser supports EcmaScript v3. Some of the embedded browsers are not identifiable by .NET Framework, so by default the functional level of contents rendered for them by IIS are down-leveled. Doing so causes advanced features like javascript to be disabled.
Resolution:
- Create a new folder within your application realm, and name it "App_Browsers" - D:\SecureAuth\SecureAuth#\App_Browsers
- Within that folder, create a .browser file.
- In this example, we will use "BoxSync.browser", that includes the following:
<browsers>
<browser id="BoxSync" parentID="Default">
<identification>
<userAgent match="Box Sync" />
</identification>
<capabilities>
<capability name="ecmascriptversion" value="3.0" />
</capabilities>
</browser>
</browsers>
- Another example for Palo Alto GlobalProtect:
<browsers>
<browser id="GlobalProtect" parentID="Default">
<identification>
<userAgent match="GlobalProtect" />
</identification>
<capabilities>
<capability name="ecmascriptversion" value="3.0" />
</capabilities>
</browser>
</browsers>
- The syntax can be used for any 'WebForm_DoPostBackWithOptions' is undefined error within an embedded browser that supports EcmaScript v3:
<browsers>
<browser id="Application Name" parentID="Default">
<identification>
<userAgent match="Application Name" />
</identification>
<capabilities>
<capability name="ecmascriptversion" value="3.0" />
</capabilities>
</browser>
</browsers>
-
This tells ASP.net that the Global Protect embedded browser supports EcmaScript v.3. There may be other <capabilities> that are needed/desired, so additional testing may be required.
Special Considerations (optional as needed): see http://msdn.microsoft.com/en-us/library/ms228122(v=vs.100).aspx for more info.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.