In xwalk projects (Danaher, Comwrap, IBM …) we need to run the importer on AEM author pages which require authentication. This is currently not possible because the HelixImportServer removes the header information in [1].
One solution we discussed with @kptdobe, @Buuhuu, @bpauli, @jckautzmann is to run the import CLI with a flag (e.g. allowHeaders) pointing to a json file (e.g. headers.json) in which the headers are defined and make the import proxy server pass the headers to the target server. For current projects, either the Cookie or the Authorisation header will be used.
In xwalk projects (Danaher, Comwrap, IBM …) we need to run the importer on AEM author pages which require authentication. This is currently not possible because the HelixImportServer removes the header information in [1].
One solution we discussed with @kptdobe, @Buuhuu, @bpauli, @jckautzmann is to run the import CLI with a flag (e.g. allowHeaders) pointing to a json file (e.g. headers.json) in which the headers are defined and make the import proxy server pass the headers to the target server. For current projects, either the Cookie or the Authorisation header will be used.
[1] https://github.com/adobe/helix-cli/blob/main/src/server/HelixImportServer.js#L99