Usage

Ping OAuth2 Frontend & LMS Functional Configuration Matrix

Note:

This section describes the matrix when LMS is used with or without frontend authentication using Ping OAuth2 access token.
enable_lms_pf_token_auth flag is used to enable LMS functional behavior.
Mashery-generated OAuth2 access token is not used here.

Sr #	enable_lms_pf_token_auth (Backend)	enable_pf_token_auth (Frontend)	Ping Auth Connector Behavior	Notes
1	config parameter is absent	config parameter is absent	Only Authentication using Ping Federate token (Frontend)	Provides flexibility to use Ping Auth for frontend call without a need to configure boolean enable_pf_token_auth . Helpful in conditions where you don't care about invocation whether it is from Connector or Authenticator or configuration from object EAV. The same is not necessarily valid for LMS. For LMS feature, we need explicit flag enable_lms_pf_token_auth that acts as a feature flag.
2	true	config parameter is absent	Both Frontend Auth and LMS Auth using Ping	See notes above.
3	false	config parameter is absent	Only Authentication using Ping Federate token (Frontend)	See notes above.
4	true	true	Both Frontend Auth and LMS Auth using Ping
5	true	false	Only Authentication using LMS token (Backend)
6	false	true	Only Authentication using Ping Federate token (Front end)
7	false	false	No Authentication using Ping	Invalid Configuration Throw an exception and block the call with 500 - Internal server error.
8	parameter is present but either null or non-boolean value	parameter is present but either null or non-boolean value	No Authentication using Ping	Invalid Configuration Throw an exception and block the call with 500 - Internal server error.