Custom SMS Provider – Basic login + Bearer token refresh | Community
Skip to main content
Silvio6
Silvio6
Level 5
February 23, 2026
Solved

Custom SMS Provider – Basic login + Bearer token refresh

  • February 23, 2026
  • 2 replies
  • 41 views

Hi, I’m configuring a Custom SMS provider in AJO.

The provider requires:

  • A login request using Authorization: Basic base64(user:password) to retrieve a short-lived token
  • A second request to send the SMS using Authorization: Bearer {token}

Since the token expires frequently, is it possible in AJO Custom SMS configuration to:

  • Dynamically generate the Basic header?
  • Handle the login call and reuse the returned token?

Or is middleware required to manage token refresh externally?

 

If Custom SMS config can’t manage this, can Custom Actions do that?

 

Thanks!

    Best answer by SatheeskannaK

    ​@Silvio6 

    A middleware component is necessary to manage the entire process.

    • The high-level integration steps are:
      • Adobe Journey Optimizer (AJO) Action: AJO initiates the workflow by triggering a Custom Action, providing the message content and the middleware's endpoint.
      • Middleware Authentication: The middleware receives the Custom Action request and performs a Basic Authentication login to the SMS Provider's Authentication API.
      • SMS Provider Token Issuance: The SMS Provider's Auth API validates the Basic Auth credentials and returns a Bearer token to the middleware.
      • SMS Sending: The middleware then uses the Bearer token to send the message request to the SMS Provider's Send API, which executes the SMS delivery.
    • Only the first step occurs within AJO; the remaining steps are handled entirely by the middleware.

    2 replies

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity AdvisorAccepted solution
    Community Advisor
    March 12, 2026

    ​@Silvio6 

    A middleware component is necessary to manage the entire process.

    • The high-level integration steps are:
      • Adobe Journey Optimizer (AJO) Action: AJO initiates the workflow by triggering a Custom Action, providing the message content and the middleware's endpoint.
      • Middleware Authentication: The middleware receives the Custom Action request and performs a Basic Authentication login to the SMS Provider's Authentication API.
      • SMS Provider Token Issuance: The SMS Provider's Auth API validates the Basic Auth credentials and returns a Bearer token to the middleware.
      • SMS Sending: The middleware then uses the Bearer token to send the message request to the SMS Provider's Send API, which executes the SMS delivery.
    • Only the first step occurs within AJO; the remaining steps are handled entirely by the middleware.
    Thanks, Sathees
      DavidKangni
      Community Advisor
      DavidKangniCommunity Advisor
      Community Advisor
      March 13, 2026

      ​@Silvio6 

      you can directly use custom action. It has basic authentication
       

      For the basic authentication mode, you need to fill in a username and a password.

      • When the authentication call is performed, the <username>:<password> string, encoded in base64, is added in the Authentication header.

      • Adobe Journey Optimizer automatically encrypts secrets defined in custom actions. Each organization’s encryption keys are securely managed in a dedicated vault tied to their organization. When credentials are displayed in the interface, they are masked by default to prevent accidental exposure.

      https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/data-source-journeys/external-data-sources#custom-authentication-mode

       

      Thanks,

      David

      David Kangni
        Terms & ConditionsAccessibility statement

        Loading footer...