Types of proxy authentication

The following shows an overview of available proxy authentication types.

To see how these types are entered, see Add a new authentication method

Basic

The Basic type requires a Username and a Password as authentication method.

Client Certificate

Client Certificate enables you to provide a certificate for authentication to the remote server. Certificates are created in the service Certificates.

OAuth 2.0

By using the OAuth 2.0 authorization framework, you can grant your own applications limited access to your APIs on behalf of the application itself.

Enter the Logon URL and the Name and Value of the header and body of your corresponding OAuth 2.0 token.

Example

Headers

Field attributes Example

Name

<Example header>

Value

https
Body

Example name Example value

grant_type

password

client_id

6779ef20e75817b79602 (GitHub)

Field attributes	Example
Name	`<Example header>`
Value	`https`

Example name	Example value
`grant_type`	`password`
`client_id`	`6779ef20e75817b79602` (GitHub)

To store the header and body values of the OAuth 2.0 request as encrypted, select the checkbox in the Encrypted column.

Neptune DXP - Open Edition user token (JWT)

You can use a JSON web token (JWT) for authentication.

Enter the name of the token in JWT Secret. You can also enter the name of the Issuer, specify the Audience and include roles and groups.

X.509

You can use the X.509 method for authentication. This is the SAP principal propagation method.

Sign With: Select a certificate to sign-in to a SAP system. Certificates are created in the service Certificates.
Assign user field to CN: Method by which a user is assigned to the common network (CN). It is recommended to use username but you can also use email.
Organization (O): Name of the organization.
Organizational Unit (OU): Name of the organizational unit.
Locality or city (L): Name of the locality or city.
State or Province (S): Name of the state or province.