Search Results

Ping Federate Authentication Connector (coming soon)

Description

  • Connector uses OAuth2 protocol for authenticating a request for service endpoint with PingFederate acting as an OAuth Authorization Server (OAuth AS).
  • Supports 'Client Credentials' and 'Resource Owner Password Credentials' grant types.

Usage

  • Ping Federate credentials 'client_id:client_secret' and base url must be configured first by customer/client
  • Confidential 'client_id:client_secret' should be encrypted for supporting 'Client Credentials' grant type
  • Confidential 'username:password' should be encrypted for supporting 'Password' grant type.
  • Default encryption algorithm will be custom-provided by Mashery but allows flexibility to use standard base64encode/base64decode.

Chaining

  • Ping Federate OAuth Connector can be chained with existing processors developed and available.
  • More details on how to chain two processors are provided in Chaining Processors.

Mashery Local Porting

Ping Federate OAuth Connector can be ported to Mashery Local customer specific bundle.
Note: Porting of this Connector can be performed by TIBCO Mashery® for a specific Mashery Local customer. Please consult TIBCO Mashery® Customer Success team.