Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-10212

Broken "Buyer Account approved" email template

XMLWordPrintable

    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide

      Configure the "Buyer Account approved" email template to use the Liquid Tag {{ provider.domain }} instead of {{ provider.external_domain }} then the email body will be delivered with the correct URL:

      Dear {{ user.display_name }},

{{ provider.name }} has approved your signup for the {{ provider.name }} API.

You may now view and manage your app/API key at https://{{ provider.domain }}/admin/

If you have problems logging into the account please contact {{ provider.support_email }}.

Sincerely,
The {{ provider.name }} API Team
      Show
      Configure the "Buyer Account approved" email template to use the Liquid Tag {{ provider.domain }} instead of {{ provider.external_domain }} then the email body will be delivered with the correct URL: Dear {{ user.display_name }}, {{ provider.name }} has approved your signup for the {{ provider.name }} API. You may now view and manage your app/API key at https: //{{ provider.domain }}/admin/ If you have problems logging into the account please contact {{ provider.support_email }}. Sincerely, The {{ provider.name }} API Team
    • Hide
      1. Ensure that account approval is enabled.
      2. Navigate to developer portal and sign up a new account with a valid email address
      3. You will receive an email with title "Red Hat API account confirmation". Click the link in the email to activate the account
      4. Navigate to and admin portal and login with admin user
      5. Navigate to Audience -> Accounts -> Listing -> created user
      6. Under "Status" click Activate and then Approve
      7. Receive another email with title "Registration now active!"
      Show
      Ensure that account approval is enabled. Navigate to developer portal and sign up a new account with a valid email address You will receive an email with title "Red Hat API account confirmation". Click the link in the email to activate the account Navigate to and admin portal and login with admin user Navigate to Audience -> Accounts -> Listing -> created user Under "Status" click Activate and then Approve Receive another email with title "Registration now active!"
    • Critical

      When testing the "Buyer Account approved" email template the Liquid Tag {{ provider.external_domain }} is not being rendered in the email body.

      Following is the email template:

      Dear {{ user.display_name }},

{{ provider.name }} has approved your signup for the {{ provider.name }} API.

You may now view and manage your app/API key at https://{{ provider.external_domain }}/admin/

If you have problems logging into the account please contact {{ provider.support_email }}.

Sincerely,

The {{ provider.name }} API Team

      In the sidekiq log we can see what is being rendered:

      Date: Wed, 11 Oct 2023 14:11:31 +0000
From: xxxxxx+3scale@hotmail.com
To: xxxxxx+gpereira07@hotmail.com
Message-ID: <6526ad13b5878_17eca9f859712@system-sidekiq-5-x58mj.mail>
Subject: Registration now active!
Mime-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit
X-SMTPAPI: {"category": "Account approved"}
X-3scale-viral:

Dear gpereira07,

Provider Name has approved your signup for the Provider Name API.

You may now view and manage your app/API key at https:///admin/

If you have problems logging into the account please contact admin@xxxxxxxxxxx.xxxxxxxx.rdu2.redhat.com.

Sincerely,
The Provider Name API Team

      If we use the Liquid Tag {{ provider.domain }} instead of {{ provider.external_domain }} the email body is delivered with the correct URL.

       

              Unassigned Unassigned
              gpereira@redhat.com Gustavo Pereira
              Marek Stastny Marek Stastny
              Daria Mayorova Daria Mayorova
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: