SecureAuth IdP Version Affected: All
Description:
How to find out what browser was used during a request to IdP.
Cause:
When troubleshooting it is sometimes necessary to know which browser was used for certain requests.
Resolution:
- Enable audit logging on the Logs tab.
- The audit log can be found in D:\SecureAuth\SecureAuthXX\AuditLogs
- The browser information is recorded as part of the user agent string supplied by browsers to the IdP.
Here's some examples for IE which identifies itself as Trident, the name of the browser engine in IE:
This is IE 11 on Windows 8.1
UserAgent="Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko"
This is
Internet Explorer 11 on Windows 8.1 Internet Explorer 7 Compatibility View
UserAgent="Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C)"
Chrome, Firefox etc. all have their own identifiers.
This is IE 11 on Windows 8.1
UserAgent="Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko"
This is
Internet Explorer 11 on Windows 8.1 Internet Explorer 7 Compatibility View
UserAgent="Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C)"
Chrome, Firefox etc. all have their own identifiers.
A site like https://browscap.org/ua-lookup can be used to translate user agents into something a bit more human readable.
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.