we set up a "on-prem" Appian instance (actually on AWS) to develop and test custom plugins (especially components).
General setup is OK, also instance is successfully registered as dev instance.
Since it is just an internally used dev instance, we decided to use something like
appian.###.internal.###.com to access Appian (left it on port 8080 for the sake of simplicity)
Static/dynamic URLs follow the same principle:
Additionally we set the parameter conf.suite.DISABLE_STRICT_DOMAIN_SECURITY=true
Unfortunately we have difficulties with the configuration of static and dynamic content URLs, so self developed components are not working properly.
Reading through documentation (https://docs.appian.com/suite/help/22.4/Post-Install_Configurations.html) and other posts (https://community.appian.com/discussions/f/administration/13390/static-and-dynamic-content-url) it is clearly stated to use 3 unique TLD.
Is there any workaround for not using 3 top-level-domains to get components working? (Appian is not using 3 TLDs on their cloud instances to differentiate static, dynamic content AFAIK)
As I mentioned, it is "just" a dev environment used by a handful of devs.
Discussion posts and replies are publicly visible
You might also try adding this parameter to the custom.properties file...conf.suite.DISABLE_SIBLING_DOMAIN_SECURITY=true
Hi,I don't find any documentation explaining what this parameter exactly allows.
Could you give more details please ?
This parameter allows you to use the same TLD for the primary and dynamic/static URL.
Otherwise (w/o the parameter) Appian would expect 3 different TLDs because of security concerns.
© 2023 Appian. All rights reserved.