Browser loses Fragment identifier '#' after redirect in RSA Access Manager 6.x
Originally Published: 2010-12-03
Article Number
Applies To
RSA Product/Service Type: Access Manager
RSA Version/Condition: 6.x
Issue
URL loses fragment identifier ( customer referred to it as "Anchor Text") after redirection to Logon Page. Example of a URL with fragment identifier
http://tools.ietf.org/html/rfc2396#section-4.1
Click on the above and it takes you to the section4.1 of the URL
Cause
It is never seen by the webserver and therefore our agent doesn't see it either, so impossible for the RSA agent to capture it to save it. The browser holds onto the reference information (never sends it) to be interpreted by the browser after the retrieval action has been successfully completed (i.e. bookmark). Unfortunately, the browser doesn't?t retain it because of the type of redirect after authentication. The browser would use it only if going directly to the page.
Resolution
In this case with IWA the redirect is done by the ct_home.asp page that is IWA protected in the ClearTrust\IWA\directory
<% If sURL <> "" Then %> <META HTTP-EQUIV="refresh" CONTENT="0;url=<%=sURL%>"> </HEAD> <% Else %>
Instead of META refresh use
response.redirect "<%=sURL%>"\
The Firefox and Chrome browsers now retain the #text. Internet Explorer 7 and 8 still don't retain it. IE may need additional config changes to work.
IE8 is listed as retaining the #text on this chart:
Related Articles
Attempts to scrub/hash JSON data elements are not always working in RSA Web Threat Detection Number of Views How to create additional SMS operators Number of Views Supported ODA SMS providers of. Number of Views Supported On-Demand Authentication (ODA) SMS providers for use with RSA Authentication Manager 8.x Number of Views Changes to the RSA Authentication Manager 8.1 Public APIs Number of Views
Don't see what you're looking for?
