Questions about Destination Selector, Asset Selector, and Server-Side Authentication

[olsalas711]

Hi Community,

We are currently testing the Destination Selector, but we’ve noticed that selecting a folder in the provided example doesn’t trigger any visible action. We’d like to understand if we are missing something in the process.

Additionally, we need a clearer understanding of how the Asset Selector works. When we select an asset, we notice that the URL of the selected asset is not returned in the callback. Could you guide us to identify if there’s a missing configuration or step?

This work is part of a proof of concept we are developing for a client in the financial sector. The objective is to integrate their on-premise CMS, hosted in a private network, with a middleware located on a public domain that is whitelisted by Adobe. The goal is to establish a secure channel allowing the CMS to connect to the middleware and retrieve asset information from AEM.

Lastly, it would be very helpful if you could provide us with an example of server-side authentication, as we would like to avoid the AuthFlow authentication method.

We look forward to your guidance and appreciate your support in moving forward with this integration.

Best regards,

Oscar Salas.

[AmitVishwakarma · Accepted solution]

1. Destination Selector:

Issue: Selecting a folder doesn't trigger any visible action.
Solution: Ensure you are using the correct destination selector implementation and that the UI is properly wired to handle the selected folder. Double-check the JavaScript or backend logic to ensure that when a folder is selected, it triggers the appropriate action (such as displaying the folder's contents or updating a field).

2. Asset Selector:

Issue: The URL of the selected asset is not returned in the callback.
Solution: Verify that your Asset Selector is properly configured. In most cases, the callback function should include the asset's path or URL. Ensure that the event listener for the asset selection properly captures the data and that the asset's URL is part of the selected asset's properties (e.g., path or fileReference).

Example of capturing the URL:

assetSelector.on('selection', function(event) {
var asset = event.selected[0]; // Assuming the first selected asset
console.log(asset.path); // This should log the path or URL
});

3. Server-Side Authentication:

Issue: You want an example for server-side authentication without using the AuthFlow.
Solution: For server-side authentication, you would typically authenticate via OAuth or basic authentication by sending the credentials with your request. Here's an example using basic authentication with cURL (adjust accordingly for your implementation):

Example using OAuth 2.0:

curl -X GET "https://<aem-instance>/path/to/resource" \
-H "Authorization: Bearer <access_token>"

Example using Basic Authentication:

curl -u <username>:<password> -X GET "https://<aem-instance>/path/to/resource"

If using OAuth 2.0:

Ensure your middleware authenticates using OAuth tokens and that AEM allows OAuth-based authentication.

4. Secure Channel between CMS and Middleware:

Use SSL/TLS to establish a secure channel between the CMS (on-premise) and the middleware. Ensure that the middleware server is properly configured with an SSL certificate and that your firewall and routing are set up to allow traffic only from the whitelisted domain.