To configure an impersonation authentication scheme, you need more than one .fcc file and more than one form. For example, you need one file and form to begin impersonation and another file and form to end impersonation. In addition, you can have a .fcc file that configures a form for successful impersonation and another .fcc file that configures a form for failed impersonation. Below are the directives that you need in the .fcc files for impersonation to succeed.
Include the following directives in a .fcc file configured to begin impersonation:
The @smpushsession=true directive instructs the Web Agent to save the impersonator's session specification and to set the session cookie to the impersonated user's session specification.
Set @username to the name of the impersonatee.
Example: @username=%USER%
Set @password to the password of the impersonator.
Example: @password=%SMSERVERSESSIONSPEC%
Note: As shown in the @username and @password examples, you can use the FCC's ability to substitute the contents of headers or cookies in directives at the time the form is posted.
Include the following directives in a .fcc file configured to end impersonation:
The @smpopsession=true directive instructs the Web Agent to end the impersonated user's session and restore the impersonator's session specification.
Set @target to the resource where the impersonator initiated impersonation.
Example: @target=/impersonators/end.htm
Set @smredirect to the resource where the impersonator initiated impersonation.
Example: @smredirect=/impersonators/end.htm
Note: Set both @target and @smredirect to the same resource. Both directives are needed.
For more information about .fcc files, see HTML Forms Authentication Schemes.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |