< Day Day Up > |
SharePoint Portal Server offers a single sign-on service that makes it easier for users to access their applications within the portal. If you embed an expense-tracking or project management system in your portal that requires a separate login, you can configure SharePoint to store user credentials and map them to their SharePoint account. Users can move from one application to another without signing into each one separately. Single sign-on maps authentication to the individual web parts. You could, for example, design a portal page with three different web parts requiring three different usernames and passwords. The single sign-on service would map all these to the appropriate credentials without prompting the user to log in again. To implement single sign-on, you must configure the single sign-on service, create a base system key, and then add application definitions for each of the applications to be integrated. Here are more detailed steps:
NOTE You cannot manage the base system key remotely. You must access the job server and specify the settings locally. This may be a long-running process, so take care to perform it at off-peak periods. The development interface for SharePoint single sign-on is extensible, so developers can add custom functionality. These changes can make the SharePoint Portal Server user interface a useful part of an enterprise portal even if you are not relying on out-of-the-box functionality. |
< Day Day Up > |