You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to ask you, if would it be possible to implement a feature so that HolodeckB2B can receive messages from partner systems using HTTPS protocol. As far as I know, HoloDeck supports HTTPS only as client. We would like to use HTTPS in server mode - configured in holodeckb2b.xml file in section:
...
Receiving messages using the current HTTP protocol is worrisome in a large company environment, security managers do not like plain HTTP-based communication.
There is a workaround for this, where the communication is HTTPS up to the firewall and HTTP within the firewall - but many of our partners do not tolerate HTTP communication within the firewall either.
Thanks for reply
Best Regards
Zsolt Szabó
The text was updated successfully, but these errors were encountered:
At the moment Holodeck B2B indeed does not include https support for incoming messages. We recommend using a proxy to receive messages over https.
However we are open to offers of sponsoring development of features. If your company is interested in sponsoring development of https support we would be happy to discuss this further.
Could you explain in a little more detail how you could imagine supporting the development of HTTPS support?
What are the expected costs for the development of the given feature, and what is the turnaround time for it to be completed?
It is possible that we can manage the positions in this matter, please write the details privately to the email address [email protected].
Dear HolodeckB2B Development Team,
We would like to ask you, if would it be possible to implement a feature so that HolodeckB2B can receive messages from partner systems using HTTPS protocol. As far as I know, HoloDeck supports HTTPS only as client. We would like to use HTTPS in server mode - configured in holodeckb2b.xml file in section:
...
Receiving messages using the current HTTP protocol is worrisome in a large company environment, security managers do not like plain HTTP-based communication.
There is a workaround for this, where the communication is HTTPS up to the firewall and HTTP within the firewall - but many of our partners do not tolerate HTTP communication within the firewall either.
Thanks for reply
Best Regards
Zsolt Szabó
The text was updated successfully, but these errors were encountered: