App runs in a Browser and does not sign-in the app

[streetgrover]

When attempting to log in to the SAP Concur Mobile App, it forces a web-browser interface within the app for any username/password entering method. After signing in, using any sign-in method (username/password, SSO, etc.) it loads the web interface and does not allow the application to open. This is not usable at all and I am frustrated that I can't get the application to work outside of the browser sign-in window within the app. This is a huge hindrance to my workflow and I can no longer upload receipts, submit reports, or book work travel like I used to.

Please address this issue with an App update or help me find a workaround.

Thanks,

Screenshots of the issue are provided below:

[johnsol5 · Accepted solution]

This morning I was able to get in, I am on IOS 18 BETA, but my users were not, so I went and checked if Concur had an app update on my device and it did. So I updated to version 10.15.1 and now I too cannot get in to Concur via mobile app.

10/01/2024 - to update readers:  I have verified with multiple iPhone users with various phones and system versions, IOS all versions work up through Concur mobile app version 10.14.0.2409031209 Even IOS Beta 18.1 (22B5054e), but as soon as you update the Concur Mobile app to any version after that it does not work.

So far with my ticket in with Concur has stated the following (i.e. major change with NO communications to Admins that I can find). I have asked for documentation of this and we are looking at our SSO now too. Will come back and update if we fix on our side. 

Concur has incorporated a relaystate parameter in the authentication request. It is crucial to collaborate with your IT team to ensure that the relaystate query string parameter is permitted/enabled. They should be able to identify where relaystate is not being passed along and determine where it is being dropped.

Depending on the IdP configuration, certain customers may be set up to use the IdP-initiated endpoint (such as Ping), which may not be configured to accept relayState. As a result, a more extensive reconfiguration of their IdP is required.

Additionally, in the same scenario, clients have the option and are encouraged to transition to SAML2, which follows a proper SP-initiated SSO flow. The effort required to reconfigure the IdP and transition to SAML2 is comparable.

[JulaM]

Hi All,

Does anyone face the same issue now with Concur app where it opens web instead of Mobile?