- Campaign v7 documentation
- Latest updates
- Release Notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- Connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Marketing Resource Management
- Distributed marketing
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Get started with workflows
- Execute a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitor workflows
- Advanced management
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Configure external accounts
- Configure Federated Data Access
- Get started with Federated Data Access
- Best practices and limitations
- Configuration guidelines
- Configuration steps
- Configure Amazon Redshift
- Configure Azure Synapse
- Configure Google BigQuery
- Configure Hadoop
- Configure Microsoft SQL Server
- Configure Netezza
- Configure Oracle
- Configure PostgreSQL
- Configure SAP HANA
- Configure Snowflake
- Configure Sybase IQ
- Configure Teradata
- Configure Vertica Analytics
- Remote access rights
- Connect to the database
- Create the data schema
- Define data mapping
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel
Configure URL permissions (on-premise)
The default list of URLs that can be called by JavaScript codes (workflows, etc.) by your Campaign Classic instances is limited. These are URLs that allow your instances to function properly.
By default, instances are not allowed to connect to outside URLs. However, it is possible to add some outside URLs to the list of authorized URLs, so that your instance can connect to them. This allows you to connect your Campaign instances to outside systems like, for example, SFTP servers or websites in order to enable file and/or data transfer.
This procedure is restricted to on-premise deployments.
As a hosted customer, if you can access Campaign Control Panel, you can use the URL permissions self service interface. Learn more
Other hybrid/hosted customers need to reach out to Adobe support team to add IP to the allowlist.
For Hybrid and On-premise deployments, the administrator needs to reference a new urlPermission in the serverConf.xml file.
Three connection protection modes are available:
- Blocking: all URLs that do not belong to the allowlist are blocked, with an error message. This is the default mode after a postupgrade.
- Permissive: all URLs that do not belong to the allowlist are allowed.
- Warning: all URLs that do not belong to the allowlist are allowed, but the JS interpreter emits a warning, so that the administrator can collect them. This mode adds JST-310027 warning messages.
<urlPermission action="warn" debugTrace="true">
<url dnsSuffix="abc.company1.com" urlRegEx=".*" />
<url dnsSuffix="def.partnerA_company1.com" urlRegEx=".*" />
<url dnsSuffix="xyz.partnerB_company1.com" urlRegEx=".*" />
</urlPermission>
By default, new implementations use the Blocking mode.
As an existing customer coming from a migration, you can temporary use the Warning mode. Analyze the outbound traffic before allowing the URLs. Once the list of allowed URLs defined, you can add the URLs to the allowlist and activate the Blocking mode.
For more information, refer to these sections:
Resources
Adobe Account
