Portal users must be authenticated to use most portal functions (except for those available to anonymous users). The portal takes advantage of the User Management Engine of the AS Java.
Basics
Creating a new administrator user using JSP— This JSP code creates a new portal user called XXXXXXX with a password of admin99 with the role of a super admin. This is useful in case your regular super admin user is locked out.
Limiting Number of Users Logged On— One of the common issues many portal projects have is to limit the number of users who can be logged on to the portal / WebAS (e.g. for WebDynpro) at any one time. This is a way to do it.
Changing UME properties using the config tool— The config tool is a good choice for making changes to UME properties, as it is available even if the Java engine won't start. Here's how to use it to change the properties or to select a different configuration file.
Some General Tips— Some generalizations that I have noticed from watching the portal implementation forum.
Virtual Groups— Sometimes you're asked if you can do role assignment based on some sort of attribute of the user - for example, an English role, a German role etc. With virtual groups, this is possible.
SSO Checklist— This is a quick checklist to help you see if SSO is set up correctly in your backend system. Please use this list before posting questions about SSO in the portal forums.
Single Sign-On and Cookies— Single Sign On (SSO) relies on cookies. Here are some FAQs about this relationship
Single Sign-On to Non-SAP Backends— One of the powerful features of the SSO ticket is that it can be used by non SAP backend applications. This page explains some of the issues involved.
Disable the user password— It is useful to be able to disable the password for a set of ABAP users. This prevents user from accessing the ABAP system directly, but they can still access through single sign on from an SAP NetWeaver Portal
Changing UME properties using the config tool