‎2007 Sep 06 5:56 AM
hi,
where is security relevent information such as Password for ITS are stored?
‎2007 Sep 06 6:01 AM
Single Sign-On with User ID and Password
Purpose
The Single Sign-On (SSO) mechanism with user name and password provides an alternative for applications that cannot accept and verify SAP logon tickets. With this SSO mechanism the Portal Server uses user mapping information provided by users or administrators to give the portal user access to external systems. The portal components connect to the external system with the users credentials.
As the user's user ID and password are sent across the network, you should use a secure protocol such as Secure Sockets Layer (SSL) for sending data.
Process Flow
There are different procedures depending on the requirements.
Single Sign-On to SAP Systems
You can access SAP Systems that do not support SAP logon tickets via Single Sign-On with user ID and password. These are SAP Systems with release 3.1I. For more information, see Configuring SSO with User ID and Password to SAP Systems.
Single Sign-On to non-SAP systems via a Java iView developed specifically for the customer
The system must be defined in the system landscape. For details, see Creating Systems.
The administrator or user must map user data to user data in the system. For more information, see User Mapping.
The iView through which the user tries to access the system must be programmed to get the mapped user data from the data repository and write the user credentials (user ID and password) in a header field of the request. The system can then log on the user with these credentials. This can be done using the Java APIs provided with SAP Enterprise Portal.
‎2007 Sep 06 6:00 AM
‎2007 Sep 06 6:01 AM
Single Sign-On with User ID and Password
Purpose
The Single Sign-On (SSO) mechanism with user name and password provides an alternative for applications that cannot accept and verify SAP logon tickets. With this SSO mechanism the Portal Server uses user mapping information provided by users or administrators to give the portal user access to external systems. The portal components connect to the external system with the users credentials.
As the user's user ID and password are sent across the network, you should use a secure protocol such as Secure Sockets Layer (SSL) for sending data.
Process Flow
There are different procedures depending on the requirements.
Single Sign-On to SAP Systems
You can access SAP Systems that do not support SAP logon tickets via Single Sign-On with user ID and password. These are SAP Systems with release 3.1I. For more information, see Configuring SSO with User ID and Password to SAP Systems.
Single Sign-On to non-SAP systems via a Java iView developed specifically for the customer
The system must be defined in the system landscape. For details, see Creating Systems.
The administrator or user must map user data to user data in the system. For more information, see User Mapping.
The iView through which the user tries to access the system must be programmed to get the mapped user data from the data repository and write the user credentials (user ID and password) in a header field of the request. The system can then log on the user with these credentials. This can be done using the Java APIs provided with SAP Enterprise Portal.
‎2007 Sep 06 6:08 AM
Can u say in which table these passwords will be stored.......