Customization
From Ogce
Contents |
Customizing the Portal
You can customize various aspects of the portal. These include the theme (look-and-feel), default guest and user layouts, and additional authentication modules (used for single-sign-on to the grid). The specific details depend on the porltet container. OGCE by default builds into the GridSphere container.
GridSphere Customization Tips
Themes
The theme specifies the look and feel of the portal. In order to modify the portal's theme, please edit the css files in src/webapp/theme/gp-demo/css. For more details on GridSphere themes, please refer to the GridSphere documentation.
Layouts
Default layouts for guest and authenticated users may be customized to suit the needs of your portal. These layout descriptors can be found in src/webapp/WEB-INF/CustomPortal/layouts. GuestUserLayout.xml and TemplateLayout.xml specify the layouts for an unauthenticated portal user and an authenticated portal user respectively. For information on editing these descriptors, please refer to the GridSphere documentation.
Single Sign-on Authentication Modules
The OGCE Portal deploys an authentication module in addition to GridSphere's default password authentication module. The portal's authentication modules can be configured to retrieve a proxy from the GridPort Repository or from configured myproxy servers on behalf of the user upon login to the portal. This proxy is stored by the portal and can be viewed using the Proxy Manager portlet. The authentication module and Proxy Manager portlet are part of the
For more detailed instructions on configuring the modules click here.
For more details on authentication modules in GridSphere, please refer to the GridSphere documentation.
Grid Certificates and Signing Policies
In order to utilize the grid portlets included in the OGCE Portal, you must have grid certificates and signing policies of the CA that your grid utilizes. The build process (during the deploy goal) copies the certificates and signing policies of the TACC and DOE CAs from src/certs to your ~/.globus/certificates directory. To customize the portal to use your grid, please ensure your certificates and signing policies are available. You may place them in src/certs and attain the install-certs maven goal.
Note: The ~/.globus/certificates directory will be checked before the other globus certificates directories, so if you already have certificates on your portal resource (for example, in /etc/grid-security/certificates), the existing certificates will not be found.
