The former will install the OpenID relying party in application scope, the latter will install it in virtual application scope. The virtual application scope allows for using different provider configurations depending on the server name. See {@link VirtualApplicationScoped}.
This API (implemented by the framework) comes along with an SPI: {@link OpenIdRelyingPartySpi} (implemented by the client application).Dialogues are used to bridge corresponding API and SPI calls (see {@link Dialogued}).
Most methods in this API require that the HTTP response is passed as a parameter. The implementation needs the response, in order to redirect the browser to the relying party. Beware not to touch the HTTP response after one of these method returns.
@author Marcel Kolsteren
|
|
|
|