You have determined that you only need to make minor adjustments in the branding of the logon screen, if any. You can perform more extensive customization of the logon screen with SAP NetWeaver Developer Studio .
Use this procedure to configure some parts of the logon screen of SAP NetWeaver Application Server (AS) Java to match the branding used by your company or provide more services to your users.
The logon screen uses two images and a cascading style sheet to branding the logon screen. See the description of the logon screen layout below.
You can enable a certificate logon link. If you configure your AS Java to support logon with X.509 certificates, users can log on with their certificate. Users no longer need to provide user ID and password.
More information: Using Client Certificates for User Authentication
For more information about how to configure other services on the logon screen, such as logon help for forgotten passwords, self-registration, or certificate enrollment, see the following:
Layout of the Logon Screen
One half of the logon screen displays a branding image. The other half of the logon screen displays a branding image for text at the top of the screen. This image is used to display the product name. Below appears the user ID and password entry fields, the Log On button, and optional links for logon support, certificate logon, client certificate creation, and self-registration.
The figure below illustrates the relative position of the various screen elements of the logon screen. It identifies the name and size of the branding images.
For the branding images, you can use any URL, but if you log on with HTTPS, external links may generate a warning about nonsecure items. Do not refer to the local file system, as this means the browser of remote clients attempt to find the image on their local file system. The content delivered by the URL always has the Multipurpose Internet Mail Extensions (MIME) type image.
The portal does not use the cascading style sheet defined by these settings.
We recommend that you deploy your images as an application (in your own namespace) or in a publicly accessible location, such as a Web server or file share, where all your clients have access rights.
Begin the entry with a forward slash (/) to begin from the root node of the AS Java, followed by the application and the path to the resource. For example: /my_app/resource/my_image.gif . Without the forward slash (/) the AS Java assumes the resource is part of the root node of the logon application under the following path:
<installation directory> / j2ee/ cluster/ apps/ sap.com/ com.sap.security.core.logon/ servlet_jsp/ logon_ui_resources/ root/
If your users only access the AS Java as a portal, deploy the images as a portal application.