BAdI Implementations for Custom-Defined Configuration

If you want to grant access to a service provider that does not appear in the list of service provider types registered in the AS ABAP, create a dedicated service provider type and declare its settings and values using BAdI implementations.

Developers need to create different BAdI implementations with the following function:

Declare settings and parameters, such as endpoint settings, supported grant types, and some additional parameters required by the service provider, for example, Google Cloud Platform or Microsoft Azure
Define the values of the additional parameters required by the service provider
Note
An implementation of the second BAdI is only necessary if the service provider defined additional parameters.

For more information, see the related link.

Declaring Settings and Parameters

You need to create a new class in the customer namespace that inherits from CL_OA2C_SPECIFICS_ABSTRACT and redefines methods as required. If you want to transport this scenario, save it on a transport request. Overwrite and redefine the methods with the settings and parameters your service provider requires.

Defining Values

You need to create a new class in the customer namespace that implements the inface IF_OA2C_CONFIG_EXTENSION. If you want to transport this scenario, save it on a transport request. Implement the method IF_OA2C_CONFIG_EXTENSION~GET_AC_AUTH_REQU_PARAMS with the parameter values your service provider requires.