BC17 Federation Service endpoint error and iOS access


A freshly installed BC17.1 throws alot of error messages in the eventviewer, my best guess is that it would be fixed if we start using SSO, and that might very well be the case in some scenarioes.

Message The Federation Service endpoint login failed because the following audience URI does not match an AppIdUri or wtrealm in server or application configuration.

How can these messages be fixed while running windows-login(if thats the case)?

Another thing, we cant get access from iOS devises.
Using an iPhone we get loginscreen, but after that, a blue circle with a white background is the only thing shown.
App is only showing logo.
Everything works on Android and windows, but iOS :-(
I have made the changes in navsettings.json
GlobalEndPoint - null,ms://businesscentral,ms://dynamicsnav,bc17.domain.dk,ms:/.../bc17.domain.dk
as MS describes Install the Business Central Mobile App - Business Central | Microsoft Docs

Any idears

Best regards Erik

No Data
  • Finally I have some updates...
    After a MS service ticket, witch did not give anything, a new iOS app is released, that fixes half of the problem.

    I now have environments that works, and also some that does not work.
    Difference as I see it, the ones that does NOT work, there is a Load Balancer or Application Gateway in front,
    those that does work have direct connection without Load Balancer or Application Gateway in front, but have a public IP on Application server (witch are not best practice)
    Android devices have no issues...
    We don't want to expose the Application server directly to the internet, and would atleast have a Load Balancer infront, preferable a Application Gateway.

    I am pretty sure I'm not the first person in the world facing this issue, but I cant find any solutions for this mess?
    I have customers and colleagues that wants this fixed, but I see no solution.

    I know its probably a security thing by Apple.

    Btw, , that error I also mentioned, have been fixed by MS in 17.3 since it was a bug in earlier versions ;-)