Close popover

Table of Contents

Creating an authentication profile

Version:

Create an authentication profile to move messages securely to and from your application with a variety of connector and server rules.

  1. In the navigation pane of Dev Studio, click Records Security Authentication Profile .

  2. In the list of authentication profiles, click Create.

  3. In the Type list, click the profile type:

    • To pass basic HTTP authentication credentials, select Basic.
    • To pass NT LAN Manager credentials, select NTLM.
    • To use OAuth 1.0 authentication, select OAuth 1.0a.
    • To use OAuth 2.0 authentication, including support for the on-behalf-of (OBO) flow and JWT bearer grant type for Microsoft Azure and other providers, select OAuth 2.0.
    • To use Amazon Web Services (AWS) security credentials. for example, for S3 repository storage, select Amazon Web Services (AWS).
    • To use Microsoft Azure storage account access, select Microsoft Azure.
  4. Enter a name and short description.

    The name must begin with a letter.

  5. Click Create and open.

  6. Configure your selected authentication profile.

  7. Click Save.

  • Configuring a Basic authentication profile

    Configure a basic authentication profile so that messages sent to and from your application use basic HTTP authentication credentials.

  • Configuring an NTLM authentication profile

    Configure an NTLM authentication profile so that messages sent to and from your application use NT LAN Manager credentials.

  • Configuring an OAuth 2.0 authentication profile

    Configure an OAuth 2.0 authentication profile to secure messages that your application sends and receives, by using an OAuth 2.0 token-based authorization process. You define OAuth 2.0 authentication profiles for Pega Platform to securely access external REST service APIs with access tokens.

  • Configuring an Amazon Web Services authentication profile

    Configure an Amazon Web Services (AWS) authentication profile so that messages sent to and from your application use AWS authentication.

  • Configuring a Microsoft Azure authentication profile

    Configure a Microsoft Azure authentication profile so that messages sent to and from your application use Microsoft Azure authentication.

  • Authentication profiles

    Create an authentication profile to move messages securely to and from your application with a variety of connector and server rules.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • OAuth 2.0 providers

    The OAuth 2.0 protocol provides your application with secure authentication in open networks with external applications, such as Facebook, and Google, over HTTPS. You define OAuth 2.0 provider data instances so that Pega Platform can access protected external resources by using access tokens.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.