000024980 - Problem exporting properties on HTTP header in RSA ClearTrust

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000024980
Applies ToRSA ClearTrust 5.5.2
RSA ClearTrust Agent 4.6 for Apache 2.0.x
Microsoft Windows 2000 SP4
Apache 2.0.49
IssueProblem exporting properties on HTTP header in RSA ClearTrust
HTTP header variables not exported even after authenticating correctly to a ClearTrust-protected resource
CauseRSA ClearTrust Agent not configured to export and publishable HTTP header variables
ResolutionTo correct this issue, ensure that the userprops webagent.conf file configuration parameter of is set with a comma separated list of HTTP header variable names that are required to be exported:

# Specifies the list of custom user properties that can be set as HTTP headers
# after successful user authentication corresponding to AuthN. For AuthZ, all
# the exportable user properties associated with the application will be published;
# this list will not be consulted.
#
# Allowed Values:
# A comma-separated list of custom user properties. Property definitions can
# be created using the RSA ClearTrust Administrative API or Entitlements
# Manager.
#
# NOTE:
# The property definition(s) should be marked as 'Publishable'.
# If wildcard is used (cleartrust.agent.userprops=*), all
# publishable user properties will be published as HTTP headers. Property
# definition(s) are case sensitive.
#
# Example:
# cleartrust.agent.userprops=title,telephoneNumber
#

cleartrust.agent.userprops=
Legacy Article IDa26179

Attachments

    Outcomes