Prerequisites
Before you set up Arbortext Content Delivery for SSO, PTC recommends that you read the PTC Identity and Access Management Help Center to understand the PTC SSO architecture, key terms, and configuration settings.
Before configuring Arbortext Content Delivery for SSO, ensure you have the following setup:
Arbortext Content Delivery 7.2.0.2 or later releases
Refer the Release Advisor page for the latest supported version of PingFederate. For installation instructions, see the PingFederate (link removed as it was not working in PDF) documentation.
New customers’ choosing to use PingFederate must contact directly with PingIdentity to purchase a PingFederate License.
If you are using a third-party Identity Provider (IdP), ensure that it is already identified and setup. The following attributes and files are provided by the IdP:
Uid (mandatory)
Email (optional)
Group used for user provisioning (optional)
Metadata file
Signing certificates (X.509 SAML signing certificates)
Update/Upgrade Prerequisites:
If you are updating or upgrading from an earlier release to 7.2.0.2 or later releases, use the following table for reference to execute query on your respective database type to support the SSO configuration.
Database
Query to be Added
Oracle database
CREATE TABLE <E3C_Schema_Name>.OAUTH_CLIENT_TOKEN 
(
TOKEN BLOB,
AUTHENTICATION_ID varchar(256) PRIMARY KEY NOT NULL
);
MS SQL database
CREATE TABLE <E3C_Schema_Name>.[OAUTH_CLIENT_TOKEN](
[TOKEN] [image] NULL,
[AUTHENTICATION_ID] [nvarchar](255) NOT NULL,
CONSTRAINT [OAUTH_CLIENT_TOKEN_PK2] PRIMARY KEY
(
[AUTHENTICATION_ID] ASC
))
PostgreSQL database
CREATE TABLE <E3C_Schema_Name>.oauth_client_token 
(
token bytea,
authentication_id character varying(255) NOT NULL PRIMARY KEY
);
* 
It is assumed that you are familiar with SSO using SAML authentication and delegated authorization (OAuth).
Arbortext Content Delivery supports the SAML 2.0 protocol for user authentication and OAuth 2.0 protocol for delegated authorization.
Was this helpful?