

Single Sign-On Service › SSO Getting Started Guide › How to Connect a CA CloudMinder Tenant to an Office 365 Tenant › Overview › The CSP Admin Tasks to Connect a CA CloudMinder Tenant to an Office 365 Tenant › Create Federation Partnership
Create Federation Partnership
This section describes how a CSP Administrator creates the necessary federation partnership.
This step requires the following information:
- [appId]
- [baseUrl]
- [certificateAlias]
- [directoryPassword]
- [directoryPort]
- [tenantId]
This step provides the following information:
- [disambiguationId]
- [entityIdLocal]
- [entityIdRemote]
- [partnershipId]
User Directory
Create another User Directory for the Tenant that performs a lookup by UPN.
Follow these steps:
- Log in to the CSP Console as CSP Administrator.
- Navigate to Infrastructure, Directory, User Directories.
- Create a new User Directory, with the following values:
- Name: [tenantId] Tenant Directory (UPN)
- Description: Alternate User Lookup
- Namespace: LDAP:
- Server: localhost:[directoryPort]
- Use authenticated user’s security context: unchecked
- Secure Connection: unchecked
- Require Credentials: checked
- Username: cn=dsaadmin,ou=[tenantId],ou=cam,o=ca
- Password: [directoryPassword]
- LDAP Search:
- Root: ou=[tenantId], ou=cam, o=ca
- Scope: Sub-Tree
- Max Time: 30
- Max Results: 0
- LDAP User DN Lookup
- Start: (&(camOffice365_UPN=
- End: )(objectclass=top)(objectclass=camUser))
- User Attributes:
- Universal ID: uid
- Disabled Flag: camEnabledState
- Password: userPassword
- Password Data: camPasswordData
Federation
Configure federation using this procedure.
Follow these steps:
- Log in to the CSP Console as CSP Administrator.
- Navigate to Federation, Partnership Federation, Entities, Create Entity.
- Enter the following values:
- Location: Local
- Type: WSFED Identity Provider
- SAML Token Type: SAML 1.1
- Entity ID: [entityIdLocal]
- Entity Name: [entityIdLocal]
- Base URL: [baseUrl]
- Disambiguation ID: [disambiguationId]
- Sign-Out Confirm URL: [baseUrl]/affwebservices/public/signoutconfirmurl.jsp
- Signing Private Key Alias: [certificateAlias]
- Supported NameID Formats: Unspecified
- Supported Assertion Attributes, Add Row:
- Confirm and Finish.
- Navigate to Federation, Partnership Federation, Entities, Create Entity.
- Enter the following values:
- Location: Remote
- Type: WSFED Resource Partner
- SAML Token Type: SAML 1.1
- Entity ID: urn:federation:MicrosoftOnline
- Entity Name: [entityIdRemote]
- Remote Security Token Consumer Service URL: https://login.microsoftonline.com
- Remote Sign-Out URL: https://login.microsoftonline.com
- Verification Certificate Alias: <blank>
- Supported NameID Formats: Unspecified
- Confirm and Finish.
- Navigate to Federation, Partnership Federation, Partnerships, Create Partnership, WSFED IP -> RP.
- Enter the following values:
- Configure Partnership:
- Federation Users:
- [tenantId] Tenant Directory: All Users in Directory
- [tenantId] Tenant Directory (UPN): All Users in Directory
- Assertion Configuration:
- Single Sign-On and Sign-Out:
- Authentication Mode: Delegated
- Delegated Authentication Type: Cloud
- Delegated Authentication URL: [baseUrl]/chs/login/[tenantId]/[appId]/
- Audience: urn:federation:MicrosoftOnline
- Security Token Consumer Service URL: https://login.microsoftonline.com
- Enable Sign-Out: checked
- Sign-Out Confirm URL: https://login.microsoftonline.com/login.srf?wa=wsignoutcleanup1.0&wreply=https%3A%2F%2Flogin.microsoftonline.com
- Sign-Out URL: [baseUrl]/affwebservices/public/wsfeddispatcher
- Signature
- Signing Private Key Alias: [certificateAlias]
- Confirm and Finish.
- Activate the Partnership.
Persistent Session
Each realm where the user logs in must be enabled for persistent sessions.
Follow these steps:
- Log in to the CSP Console as CSP Administrator.
- Navigate to Policies, Domain, Realms.
- Modify all realms where users login:
- For example, for the basic Authentication the Realm: [tenant_chsforms_realm_es]
- Session
- Persistent Session: Persistent
Security Token Service
This step requires:
A Security Token Service must be created on the Secure Proxy Server.
Follow these steps:
- Login to the Secure Proxy Server Admin UI
- Navigate to Web Services, Security Token Service, Add.
- Enter the following values:
- STS Name: [partnershipId]
- STS Context: /[partnershipId]
- Click OK and Save
- Restart the Secure Proxy Server.
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|