Configure Authentication for P4S 2010

Integrate Software AG Products Using Digital Event Services : MashZone NextGen Help : Appendix : Administration : MashZone NextGen Add-On for SharePoint (P4S) : P4S Configuration and Administration, SharePoint 2010 : Configuring MashZone NextGen Add-On for SharePoint 2010 : Configure Authentication for P4S 2010

The tasks you need to complete to configure authentication between MashZone NextGen Add-On for SharePoint (P4S) and MashZone NextGen Servers depends on the authentication plan you need to implement:

For SSO + Token Authentication, you use the Secure Store Service to manage user credentials for MashZone NextGen Servers. In addition, this uses tokens managed by the Token Service from P4S and authentication configuration in MashZone NextGen Server connections.

Configuration steps include:

1. Configure the Secure Store Service.

2. Once the Secure Store Service is configured, you Create Secure Store Target Applications to hold user credentials for the MashZone NextGen Servers in your environment.

3. Then Create or Manage SSO Token Server Names to manage user token IDs.

4. And finally configure authentication properties for each MashZone NextGen Server connection. See Add a MashZone NextGen Server Connection to SharePoint or Edit a MashZone NextGen Server Connection for instructions.

For No SSO + Cookie Authentication, you must configure cookie forwarding authentication in the properties for each MashZone NextGen Server connection. See Add a MashZone NextGen Server Connection to SharePoint or Edit a MashZone NextGen Server Connection for instructions.

Cookie forwarding is enabled for user connecton overrides by default, so no additional configuration is required.

For No SSO, Manual Authentication, you must:

Clear all authentication properties in each MashZone NextGen Server connection. See Add a MashZone NextGen Server Connection to SharePoint or Edit a MashZone NextGen Server Connection for instructions.

And Disable Cookie Forwarding for MashZone NextGen Server Overrides.

For more information on the requirements and user experience of these authentication designs, see Authentication Designs for P4S 2010.

Contact Support | Community | Feedback