In this use case, the Service Provider needs to single sign-on with an Identity Provider that has OpenSSO Enterprise installed in the Identity Provider environment. But the Service Provider does not want to install the full-featured OpenSSO Enterprise just to enable federation. The Service Provider cites one or more of the following reasons for not installing OpenSSO Enterprise:
The Service Provider is small company that provides one application as only part of their service.
The Service Provider wants identity federation at minimum cost.
Installing OpenSSO Enterprise would require investments in hardware, services, and human resources that the Service Provider does not want to make.
Installing OpenSSO Enterprise would require the Service Provider system administrators to be proficient in implementing identity federation protocols in order to configure and maintain the OpenSSO Enterprise federation deployment.
The Service Provider wants to quickly enable federation in their environment in a very short timeframe.
The Service Provider wants only to implement single sign-on with the Identity Provider and retrieve some user attributes for customizing the service to the user. The Service Provider does not want to install a full-featured federation solution and just to use two features.