Oracle Application Framework Developer's Guide (pages 1441-1442)

Oracle Application Framework Developer's Guide (pages 1441-1442)

When you take advantage of accelerated validation, each user gets a unique encryption key for their session. For tools such as Load Runner, where content generated for one user needs to be replayed for another user, the unique encryption key poses a problem because the generated URL changes each time a page is accessed. OA Framework provides fixed key 

support to work around this issue by allowing certain users to have a fixed encryption key for all their user sessions.

To enable fixed key support, set the profiles FND: Fixed Key Enabled and FND: Fixed Key. The profile FND: Fixed Key Enabled allows you enable the use of a fixed encryption key for accelerated validation for a user. If you enable this profile, you can then use the FND: Fixed Key profile to specify what that fixed key is for the user.

Load Runner users should set the FND: Fixed Key Enabled profile to Y at their user level and also specify a value for their FND: Fixed Key profile.

Usage Notes

1.             Due to an issue in AOL/J for guest sessions, please set the fixed key profiles so that fixed key support is enabled for the guest user "GUEST".

2.             Successful fixed key support assumes that URLs remain the same across sessions. This includes having a consistent transactionID parameter in the URL. Using a transactionID generated from an   

          earlier run of Load Runner should not affect results.

3.             You should always encrypt URL parameters using OA Framework provided mechanisms, such as token substitution and OAPageContext.encrypt. This ensures that the fixed encryption key is used, if enabled. If you encrypt a parameter by calling OAPageContext.encrypt and then pass in a different key, the URL constructed will not be consistent and as a result, the URL integrity will fail, causing the Load Runner usage to fail for this page.