search cancel

Error : WASUSERNAME is blank or invalid in ERP Agent for SAP WebAS

book

Article ID: 53957

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On SITEMINDER

Issue/Introduction

When initially configuring the ERP Agent for SAP Web AS, the following
error may appear in the SAP logs:

  "WASUSERNAME is blank or invalid"

 

Cause

 

The first thing to check is that a protected realm has been configured
for the resource in question, and that a user attribute response named
"WASUSERNAME" has been set to an appropriate user attribute, such as
"uid". If this has been done, confirm the front-end Web Agent is
adding this response by looking within the Web Agent trace log for the
following message:

  
  "Setting custom HTTP header variable: 'wasusername=testuser' from
   Policy Server"

If the ERP Agent is still not finding WASUSERNAME, check the response
attribute name for case-sensitivity. The ERP Agent requires
"WASUSERNAME" to be in all capitals; as seen from the example above,
that response was erroneously all lowercase, and will cause the
"WASUSERNAME is blank or invalid" message.

 

Resolution

 

The first thing to check is that a protected realm has been configured
for the resource in question, and that a user attribute response named
"WASUSERNAME" has been set to an appropriate user attribute, such as
"uid". If this has been done, confirm the front-end Web Agent is
adding this response by looking within the Web Agent trace log for the
following message:
  
 

  "Setting custom HTTP header variable: 'wasusername=testuser' from
   Policy Server"

If the ERP Agent is still not finding WASUSERNAME, check the response
attribute name for case-sensitivity. The ERP Agent requires
"WASUSERNAME" to be in all capitals; as seen from the example above,
that response was erroneously all lowercase, and will cause the
"WASUSERNAME is blank or invalid" message.