PI54723: APPSCAN SOURCE APPSCANSERVERDBMGR.BAT APPENDS 9443/ASE TO SERVER URL

AppScanSource-Windows-9.0.3.3-fixpack
AppScanSource-MacOSX-9.0.3.3-fixpack
AppScanSource-Linux-9.0.3.3-fixpack

APAR status

• Closed as program error.

Error description

• Observed behavior:
  When registering AppScan Source database with ASE using
  appscanserverdbmgr script, it appends 9443/ase even though the
  user input contains a valid port number and instance name.
  This makes the information entered as invalid and thus
  connection fails.
  
  eg:  if a user enters a valid server info like:
  https://some.host.name:9443/ASE , it will be changed to
  https://some.host.name:9443/ASE/ase automatically and that fails
  the connection.    In another example,
  https://win12r2ase903.rcsnl.ams.nl.ibm.com:9463/ases becomes
  https://win12r2ase903.rcsnl.ams.nl.ibm.com:9463/ases:9443/ase
  
  Expected behavior:
  When registering AppScan Source database with ASE using
  appscanserverdbmgr script it is expected to accept customer
  provided server and instance information.   It would be nice to
  add the port and instance information only if that information
  is not already entered by user.
  
  Some customers use, multiple server instances  to
  identify servers installed in different locations, such as "ke"
  for an instance in Kenya, "ch" for an instance in Switzerland
  and this automatic update of server name causes trouble to
  users.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users who would configure more than one instance of IBM  *
  * Security AppScan Source Enterprise and try to connect to     *
  * those instances from IBM Security AppScan Source.            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If a user configure more than one instance of AppScan Source *
  * Enterprise and try to connect to that instance from AppScan  *
  * Source, AppScan Source would append /ase at the end of       *
  * connection URL which will lead to connection failure.        *
  *                                                              *
  * For example, if the configured URL looks like                *
  * https://aseServer:9443/instance1, without this fix that URL  *
  * is changed to https://aseServer:9443/instance1/ase which     *
  * would become invalid.                                        *
  *                                                              *
  * The correct and expected URL would be                        *
  * https://aseServer:9443/instance1.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The server connection code of AppScan Source is fixed so now the
  reported issue no longer happens.
  

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

• Fixed component name

  SEC APPSCAN SRC

• Fixed component ID

  5724Z3400

Applicable component levels

• R880 PSY

     UP

• R900 PSY

     UP

• R901 PSY

     UP

• R902 PSY

     UP

• R903 PSY

     UP