# EDIINT AS2 with Cyclone

**URL:** <https://techcommunity.softwareag.com/t/ediint-as2-with-cyclone/107981>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [December 17, 2002, 10:29pm UTC](https://techcommunity.softwareag.com/t/ediint-as2-with-cyclone/107981 "2002-12-17T22:29:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [December 17, 2002, 10:29pm UTC](https://techcommunity.softwareag.com/t/ediint-as2-with-cyclone/107981/1 "2002-12-17T22:29:08Z")

</div>

I am currently testing this and have outbound working well. Inbound however seems to be an issue. Apparently Cyclone does not support placing a userid and password on the URL they use to invoke wm.EDIINT:receive. We are using reverse invoke and the internal server requires userid and password authentication. Does anyone know of options to get around this?

---

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [December 18, 2002, 10:56am UTC](https://techcommunity.softwareag.com/t/ediint-as2-with-cyclone/107981/2 "2002-12-18T10:56:53Z")

</div>

If you are useing HTTPS with Cyclone you can try using certificate and map Cyclone’s client certificate to a user account on your internal IS server. This way Cyclone does not need to provide it the certificate will work as auth.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:05pm UTC](https://techcommunity.softwareag.com/t/ediint-as2-with-cyclone/107981/3 "2021-04-02T15:05:00Z")

</div>


