Skip to main content
A user with the Configuration Manager role must register the certificate in SAP Fieldglass before the connection can be made.

​
Register your certificate

Certificate authentication links a public certificate to a valid, active SAP Fieldglass user,
so no username or password is sent with the token request.

1

Register the certificate in Configuration Manager

Obtain the public certificate to be used for authentication, then sign in to
SAP Fieldglass
with the Configuration Manager role and choose the Manage Crypto Assets tile. The
Encryption Keys and Certificates page opens.

  • Use an X509 certificate issued by a trusted Certificate Authority (for example, DigiCert) or the SAP Cloud Root Certificate Authority.
  • Choose New. The Create Asset page opens.
  • Category: X509
  • Public Certificate: the full certificate text, including the Begin Certificate and End Certificate lines
  • Notification Email ID: the email contact to notify when the certificate is about to expire
  • Choose the Auto-Activate option to make the certificate immediately active.
  • Under Extended Key Usage, link the certificate to a valid, active user.
  • Choose Create to save the certificate in SAP Fieldglass.
2

Copy the certificate and private key

Copy the Certificate and the matching Private Key across. Include the full contents of
each, with their Begin and End lines.

3

Find your environment URL

The Environment URL is the hostname of your SAP Fieldglass environment, without the
protocol and without a trailing slash. Read it from the address bar while signed in to
SAP Fieldglass.

  • Format: <company>.fgvms.com
  • Example: www.fieldglass.net
4

Find your authentication URL

The Authentication URL is a separate host used for the token request. The company name
that is part of it is followed with “-auth”.

  • Format: <company-code>-auth.<region>.fieldglass.net
  • Example: acme-auth.eu.fieldglass.net
  • Not all test environments are configured for certificate authentication. You may need to submit a request to have it configured.
  • Application Key: the X-ApplicationKey value, optional for Connector, Identity (SCIM), and Reporting APIs.
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.