Authentication schemes are used for UMEprogrammatic authentication only.
Authentication schemes are defined in the authschemes.xml file, which you can change using the AS Java Config Tool.
For more information, see Changing the authschemes.xml File in the portal documetation.
An authentication scheme is a definition of what is required for an authentication process. This includes:
You use authentication schemes to define what type of authentication is required for a certain application. Portal iViews and Web Dynpro applications always use authentication schemes. Web applications may use them when they use UME programmatic authentication.
By assigning an authentication scheme to an application, you specify the type of authentication required for that application. You can also use authentication schemes enable pluggable authentication for applications using UME authentication. You can easily 'plug in' additional authentication schemes without having to change each individual application.
If you change the authentication scheme referenced by default , you automatically change the authentication scheme used by all Web Dynpro applications as well.
For more information, see the portal documentation.
The AS Java is shipped with a set of authentication schemes. These are defined in the authschemes.xml file.
The following authentication schemes are shipped with SAP NetWeaver Application Server for Java:
Name of Authentication Scheme | Description | Login Module Stack | Referenced by |
---|---|---|---|
uidpwdlogon |
Requires form-based logon with user ID and password. |
ticket |
default, UserAdminScheme |
certlogon |
Requires authentication using client certificates. |
client |
|
basicauthentication |
Uses the Basic Authentication feature of the HTTP protocol. |
ticket |
|
header |
Allows authentication using external Web access management products. |
header |
|
anonymous |
Provides a very basic form of anonymous logon. A logon ticket is not issued. |
|
|