DocumentationAEM as a Cloud ServiceUser Guide

Navigating to Screens Services Provider setup-screens-services-provider

Last update: Tue Jul 23 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • Developer
  • User

Introduction introduction

Screens Services Provider, allows the content author, developers, and administrators to manage displays and players for content playback once the content is added to the channels. Once the users are given access to AEM Cloud Service, they should be able to log into Screens Services Provider.

This section describes how to set up Screens Services Provider.

Objective objective

The following section how to configure and set up Screens Services Provider.

Steps to Set up Screens Services Provider screens-services-provider

Follow the steps below to set up Screens Services Provider:

  1. Navigate to Screens Services Provider from here.

    note caution
    CAUTION
    If you have access to multiple organizations, ensure that you have logged into correct Organization. To change your organization, click the Org name from the top right-hand corner of the screen and choose the required organization to which you need access.

  2. Click the gear icon next to Project (upper-left corner)

    image

  3. Enter the following details in the Edit Settings dialog box.

    • Publish Url - AEM publish URL (for example, https://publish-p12345-e12345.adobeaemcloud.com)
    • Author Url - AEM author URL (for example, https://author-p12345-e12345.adobeaemcloud.com)
    note note
    NOTE
    Ensure you create and publish at least one AEM Screen Channel before configuring the AEM under Screens Service Provider. To create a channel, navigate to /screens.html on your content provider.

    image

  4. Click Save to connect to Screens content provider.

  5. In case you have configured the AEM publish instance to allow access only to trusted IP addresses by Cloud Manager’s IP Allowlist feature, you need to configure a header with a key value in the settings dialog as shown below.
    The IPs which need to whitelisted also need to moved to the configuration file and need to be unapplied from the Cloud Manager settings.

    image
    The same key needs to be configured at AEM CDN configuration. It is recommended to not put the header value directly in GITHub and use a secret reference.
    A sample CDN config is given below:

    code language-kind: 
        version: "1"
    metadata:
      envTypes: ["dev", "stage", "prod"]
    data:
      trafficFilters:
        rules:
          - name: "block-request-from-not-allowed-ips"
            when:
              allOf:
                - reqProperty: clientIp
                  notIn: ["101.41.112.0/24"]
                 reqProperty: tier
                  equals: publish
            action: block
          - name: "allow-requests-with-header"
            when:
              allOf:
                - reqProperty: tier
                  equals: publish
                - reqProperty: path
                  equals: /screens/channels.json
                - reqHeader: x-screens-allowlist-key
                  equals: $\
    {CDN_HEADER_KEY}
            action:
              type: allow

  6. Select Channels from the left navigation bar and click open in content provider.

    image

  7. Screens Content Provider opens in another tab that lets you create your content.

    image

What’s Next whats-next

After you have learned how to set up Screens Services Provider, navigate to Using Screens Content Provider for more details.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab