Skip to main content
Solved

Cloud MWO end points

  • November 1, 2022
  • 6 replies
  • 151 views
T
Sidekick (Partner)
Forum|alt.badge.img+8

We are implementing MWO for our Cloud customer (21R2). Accessing MWO from outside the company network is of course necessary, but we have not been able to establish a controlled access. The documentation we followed is here: https://docs.ifs.com/techdocs/22r1/070_remote_deploy/090_exposing_to_internet/

We enabled the following endpoints at the network administration side:

Aurena Native    /mob/ifsapplications/projection/v1/MobileClientRuntime.svc/*
Aurena Native    /mob/ifsapplications/projection/v1/MobileAttachments.svc/*
Authentication    /auth

However, this was not enough. The MWO Maintenance application was not able to connect. Only after we enabled also the root directory (“/”) we successfully connected using the MWO app. But that also exposed the entire IFS Aurena client to outside network, so this is not acceptable.

Do you guys have experience of a clear set of endpoints that needs to be included so that MWO apps can access the environment?

Best answer by Tuukka

We finally managed to resolve this. The paths we used were:

/auth/

/mob/ifsapplications/

To clarify, their network software had a “Contains”-type validation for the HTTP requests, so we had to leave out the asterisks (*). In some other setup they might be necessary.

Thank you both for your help!

6 replies

Dar
Hero (Employee)
Forum|alt.badge.img+5
  • Dar
  • Hero (Employee)
  • November 1, 2022

you need to allow /mob/ifsapplications/* 

kathlk
kathlk
Hero (Employee)
Forum|alt.badge.img+14
  • kathlk
  • Hero (Employee)
  • November 1, 2022

This is missing in the current documentations and we will update it to fix as you only need “/mob/ifsapplications/* ” to access native mobile

Regards KATHUK
T
Sidekick (Partner)
Forum|alt.badge.img+8
  • Tuukka
  • Author
  • Sidekick (Partner)
  • November 1, 2022

We already tried with having only “/mob/*” as the limiting factor, but that did not help. It seems like we need something else in addition to “mob” and “auth”?

kathlk
Hero (Employee)
Forum|alt.badge.img+14
  • kathlk
  • Hero (Employee)
  • November 1, 2022

‘Auth’ is common for both Native and web. We do not use any other end point apart from ‘mob’ and ‘auth’. But could this be because of the definition is incorrect in auth in the doc? Doc has the below definition. Did you try /auth/*?

Authentication /auth

. 

Regards KATHUK
kathlk
Hero (Employee)
Forum|alt.badge.img+14
  • kathlk
  • Hero (Employee)
  • November 7, 2022

Hi, Did you manage to resolve your issue? 

Regards KATHUK
T
Sidekick (Partner)
Forum|alt.badge.img+8
  • Tuukka
  • Author
  • Sidekick (Partner)
  • Answer
  • November 9, 2022

We finally managed to resolve this. The paths we used were:

/auth/

/mob/ifsapplications/

To clarify, their network software had a “Contains”-type validation for the HTTP requests, so we had to leave out the asterisks (*). In some other setup they might be necessary.

Thank you both for your help!

kathlk
Technical Toby
Terms & ConditionsCookie settingsAccessibility statement