Knowledge Base > Automation Engine and Target Systems > SAP > Problem with Password Assignment to SAP

Problem with Password Assignment to SAP

After Updating to SAP NetWeaver 2004s and Later, CPIC User Could No Longer Log On

Symptom

Password-based logon attempts (to ABAP systems as of Release 7.00 / NetWeaver 2004s / SAP ERP 2005) fail, although the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. has entered a supposedly correct passwordA secret combination of characters for a Automation Engine user. in a front-end componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. or in a destination (of another system). However, a (direct) SAPGUI logon with the same password is successful.

Reason

ABAP systems as of NetWeaver 2004s (7.00) support passwords of up to 40 characters and differentiate between uppercase and lowercase. In earlier ABAP Releases (prior to 7.00), passwords could only be comprised of a maximum of 8 characters, whereby lowercase letters that were entered were automatically changed to uppercase letters.

If, in a newer ABAP system (as of Release 7.00), a downwardly incompatible password is unknowingly granted (see below), and if the front-end or middleware components are not able to process such passwords correctly, logon problems inevitably occur.

This is usually due to the (invisible) automatic conversion from lowercase to uppercase letters. The problem is that the password entered by the user does not arrive at the server in the same form, but is changed either during input or during the transmission (in which many components are involved).

Term definitions


Solution

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH