Appendix : Administration : MashZone NextGen Add-On for SharePoint (P4S) : P4S Configuration and Administration, SharePoint 2007 : Configuring MashZone NextGen Add-On for SharePoint 2007 : Configure Authentication for P4S 2007
Configure Authentication for P4S 2007
 
Configure the SSO Service in Windows
Configure the SSO Service in SharePoint
Create SSO Applications for P4S
Configure SSO Token Server Names for P4S
Disable Cookie Forwarding for MashZone NextGen Server Overrides for Sites
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 SSO 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. If the SSO Service is not already configured, you must Configure the SSO Service in Windows and Configure the SSO Service in SharePoint.
2. Once the SSO Service is configured, you Create SSO Applications for P4S to hold user credentials for the MashZone NextGen Servers in your environment.
3. Then Configure SSO Token Server Names for P4S to manage user token IDs.
4. And finally configure authentication properties for each MashZone NextGen Server connection. See Configure MashZone NextGen Server Connections in SharePoint 2007 for instructions.
*For SSO + Cookie Authentication, you must configure cookie forwarding authentication in the properties for each MashZone NextGen Server connection. See also Configure MashZone NextGen Server Connections in SharePoint 2007 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 also Configure MashZone NextGen Server Connections in SharePoint 2007.
For more information on the requirements and user experience of these authentication designs, see Authentication Designs for P4S 2007.
Copyright © 2013-2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback