Editing HTTP System Properties 
The template for an HTTP system defines the specific parameters needed by URL-based iViews to connect to secured HTTP sites using SSO. The pre-authentication can occur on either the client or server side:
Client: The HTTP Authentication Assistant (see table below) performs the authentication process transparently, the iView is loaded, and the user is connected without having to provide identification.
Server: The iView developer calls the HTTP Authentication Assistant on the server side. The back-end application returns the headers, the AA adds the headers to the request, and the user is connected to the application without having to provide identification.
The HTTP system that you create inherits the properties of the template, some with default values, others that require the setting of values. Not all the template properties can be edited, and not all are necessary to establish a connection to the site you need. You edit the system by inserting needed property values and by modifying default values, if necessary.
The table below lists the properties needed to define connectivity to a secured site. Each has an explanation of the value that should be set.
Procedure
From the top-level navigation bar, choose
System Administration 
System Configuration 
.From Detailed Navigation, choose System Landscape.
In the Portal Catalog, right-click the system whose properties you want to edit, and from the drop-down list choose
Open Object . This opens the System Landscape Editor.Set your HTTP system properties according to the details in the table below.
HTTP System Properties Property
Value/Comments
Category: User Management
User Mapping Type
Defines the type of user mapping needed for connection; who can perform user mapping
Valid values: user/admin/admin,user
For more information, see System Properties for User Mapping.
Category: HTTP Authentication
Authentication Method
Select one of the following:
GET: Basic method for transferring parameters
POST: Enables transfer of heavy data within navigation; not seen in URL
Basic Authentication: Not possible from client side
Other: Choose this option if the site requires more than User Name and Password for proper authentication. This choice entails follow-up coding to produce a viable service; see Example, below.
Authentication Type
Client: Browser performs authentication
Server: Portal server performs authentication. This choice entails follow-up coding to produce a viable service; see Example, below.
Authentication URL
URL path must include any other parameters that the secured site requests, apart from User Name and Password.
Custom Authentication Service ID
Relevant only for Other authentication method
Enter the Key of the service that implements the authentication; see Example, below.
Enable Authentication Assistant
Yes: Enables the service
No: Authentication Assistant process will not function and authentication will not be performed.
Permanent Authentication (client-side only)
Used to determine if authentication will be performed once per session or with each iView refresh
Relevant only when using client-side authentication
URL Parameter for Password
Must be defined according to the (coded) parameter label used by the target site
Relevant only for GET and POST authentication methods
URL Parameter for User Name
Must be defined according to the (coded) parameter label used by the target site
Relevant only for GET and POST authentication methods
Assign an alias to the system. For more information, see System Aliases.
Map users to the system. For more information, see User Mapping.
Example
See SAP Note 779865 for information and examples of editing HTTP systems when using:
Authentication Type: Server
Authentication Method: Other