Skip to main content

​
OAuth Server-to-Server authentication method is not available

Confirm that the credential creator is assigned as a Developer on the intended product profile and that the profile includes the AEM Sites service, as described in Step 2 and Step 3 of the setup guide.

​
AEM CS Sites Content Management product profile is missing

Go back to Step 2 of the setup guide and verify the following:
  • Your Adobe organization owns the AEM environment you intend to use with Profound.
  • The environment is modernized for API access as instructed in Adobe’s Set up OpenAPI-based AEM APIs guide.

​
Profound can’t save the AEM credentials

Confirm the following:
  • All connection values are correct and match the values of your OAuth credential from Step 5 of the setup guide.
  • Your OAuth credential uses the AEM Sites Content Managers - author… product profile. Check this in the Adobe Developer Console. If it doesn’t, repeat Step 2 of the setup guide.
  • The config pipeline that deploys your API configuration (api.yaml) ran successfully. Check the Pipelines section of your AEM program page in Adobe Cloud Manager. If it didn’t, repeat Step 6 and Step 7 of the setup guide.
  • The client ID of the OAuth credential is in the correct place in the api.yaml configuration file, as instructed in Step 6 of the setup guide.
  • An Author IP allowlist isn’t blocking Profound. Learn more in Adobe’s Manage IP Allow Lists guide.
    If you have to apply an Author IP allowlist, contact Profound Support to obtain the current Profound outbound IP addresses rather than reusing values from an old guide or ticket.
  • If you’re using a sandbox environment, it’s online and not hibernated. Learn more in Adobe’s Hibernate and De-Hibernate Sandbox Environments guide.

​
Content Fragment Models don’t appear in Profound

This usually means either the Content Fragment Model isn’t allowed for the folders you use with Profound, or your OAuth credential’s technical account lacks the permissions to manage Content Fragment Model configuration. Confirm the following:
  • The Content Fragment Model is enabled and allowed on your assets folder. Learn more in Adobe’s Content Fragment Models documentation.
  • The technical account’s service group has permissions to manage the Content Fragment Model configuration. With the setup described in the setup guide, your technical account should already have the necessary permissions to read and manage your AEM content. If it doesn’t, manage permissions for specific folders and files in your AEM environment as described in Adobe’s Product Profile and Services user group permission management guide.
Grant the AEM OAuth credential’s technical account the narrowest permissions that support the Agent nodes you intend to use in Profound. Scope create and update access to approved folders only.

​
Folders don’t appear in Profound

  • Go back to Step 5 of the setup guide and confirm that the Scopes connection value for your Profound AEM integration matches the scopes value of your AEM OAuth credential.
  • Confirm that the scopes value includes aem.fragments.management and aem.folders. If it doesn’t, don’t add the missing scopes by hand. Confirm instead that you completed all prerequisites in Step 2 and Step 3 of the setup guide.
  • Confirm that the technical account’s service group has the permissions it needs to manage content in the /content/dam folder in your AEM environment. To add permissions for specific folders and files, follow Adobe’s Product Profile and Services user group permission management guide.

​
Create or Update Content Fragment node returns a permissions error

This usually means your AEM OAuth credential is authenticated but doesn’t have the required repository access. Follow Adobe’s Product Profile and Services user group permission management guide to grant the service group that contains your AEM technical account the create or update permissions it needs for the folder you use with Profound.