PH02497: "SESSION REQUEST SAME AS LOGIN REQUEST" IS SHOWN WHEN A LOGIN SEQUENCE HAS TWO REQUESTS

APAR status

• Closed as fixed if next.

Error description

• 1.Expected behavior:
  When validating a login sequence; an error "Session request same
  as login request" should not be reported as the validation
  status when the Login request (containing username and password)
  does not match the In-session request.
  
  2.Observed behavior:
  When a login sequence has two requests; the login and the
  In-session request; that are similar in format, validation of
  this sequence reports "Session request same as login request"
  even though the two requests are visually verified as being
  different.
  
  3.Workarounds:
  The validation status is merely an indicator for attempting to
  help configure a good login sequence.
  It does not prevent the scan from running so as long as the
  login request and insession requests look good and a valid
  insession pattern is selected then it should be possible to
  still start the scan via Scan > Explore Only or Scan > Full Scan
  in AppScan Standard.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * none                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * wont fix                                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels