Login not working into desktop team app from external SAML identity

Dalip Choudhary 1

Hi Team,

I raised a question on different community forum. question is

https://answers.microsoft.com/en-us/msteams/forum/all/calling-localhost-while-login-flow-not-happening/ab8f6f22-1a2e-4ff3-b8ae-ce8c4f3afc30

Could you please help me on this?

Detailed explanation:

Hi Team,

We have added a federated domain under my microsoft account. this federated domain, will redirected user to external SAML identity provider. Everything is working as expected in chrome or edge browser. When i am trying to login in desktop microsoft team app, At the time of rendering login page of external SAML identity provider, calling one ajax call to localhost (As login flow in happening on user's machine.). Assuming that a localhost background service is running on user's machine.

In my case when my ajax call is going to "https://somedomain:5596/auth". but I am getting below error.

Does embedded web view supports calling cross domain api call? over https or http?

loginissue

Dalip Choudhary 1 Reputation point

2024-05-30T02:38:10.57+00:00

Hi Team,

We have added a federated domain under my microsoft account. this federated domain, will redirected user to external SAML identity provider. Everything is working as expected in chrome or edge browser. When i am trying to login in desktop microsoft team app, At the time of rendering login page of external SAML identity provider, calling one ajax call to localhost (As login flow in happening on user's machine.). Assuming that a localhost background service is running on user's machine.

In my case when my ajax call is going to "https://somedomain:5596/auth". but I am getting below error.

Does embedded web view supports calling cross domain api call? over https or http?
Prasad-MSFT 5,986 Reputation points Microsoft Vendor

2024-05-30T06:34:38.04+00:00

The error you're encountering when making an AJAX call to "https://somedomain:5596/auth" from within the Microsoft Teams desktop app suggests that there might be a Cross-Origin Resource Sharing (CORS) issue. The embedded web view in the Teams desktop app does support cross-domain API calls.

Ensure that your server is configured to allow cross-origin requests from the Teams domain. This typically involves setting the Access-Control-Allow-Origin header to allow requests from the Teams client domain or using a wildcard (*) to allow all domains, which is less secure.

Make sure that the AJAX call is being made over HTTPS, as the Teams client requires secure connections for loading external content. If your local service is running on HTTP, it might be blocked due to security policies
Dalip Choudhary 1 Reputation point

2024-05-31T11:27:12.4266667+00:00

@Prasad-MSFT : I checked everything and looks good. Desktop native team app is creating problem. when i trying to login using system browser, it is working fine and i can see ajax call in network history.

Below is the Ajax call network (in chrome browser): and i assuming same thing will be done by webview.

Request URL:

https://localhost:44367/auth

Response Headers:

Access-Control-Allow-Headers: *****

Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS

Access-Control-Allow-Origin: https://parent.abc.com

Cache-Control: no-store, no-cache

Content-Length: 0

Date: Fri, 31 May 2024 11:18:12 GMT

Pragma: no-cache

Referrer-Policy: strict-origin-when-cross-origin

Server: Kestrel

Strict-Transport-Security: max-age=63072000; includeSubdomains; preload

Request Headers:

:authority: localhost:44367

:method: GET

:path: /auth

:scheme: https

Accept: /

Accept-Encoding: gzip, deflate, br, zstd

Accept-Language: en-US,en;q=0.9,hi;q=0.8,en-IN;q=0.7

Origin: https://parent.abc.com

Priority: u=1, i

Referer: https://parent.abc.com/

Sec-Ch-Ua: "Google Chrome";v="125", "Chromium";v="125", "Not.A/Brand";v="24"

Sec-Ch-Ua-Mobile: ?0

Sec-Ch-Ua-Platform: "Windows"

Sec-Fetch-Dest: Request URL:

https://localhost:44367/auth

Please suggest next step?

@Microsoft Team @Microsoft Teams Admin
Prasad-MSFT 5,986 Reputation points Microsoft Vendor

2024-06-05T13:03:39.3066667+00:00

Could you please refer this and check if it helps?
https://onexception.dev/news/1278294/microsoft-team-ajax-call-failure-with-saml-identity
Dalip Choudhary 1 Reputation point

2024-06-07T15:00:59.5233333+00:00

@Prasad-MSFT : any update please?

I want to call client side localhost service from external IDP login html page. When login page will start to render in microsoft web view, on document.onload, we are calling that ajax call.

there is problem. localhost call is giving 404 status code.

Team Error Code is: 2603

I have added a dummy dns name on route53 with name as parent.custmodomain.local and it will point to 127.0.0.1

On chrome browser, everything is working fine. but in microsoft team, it is creating problem.

@msft5324 @Microsoft Technical @Development Microsoft
Prasad-MSFT 5,986 Reputation points Microsoft Vendor

2024-06-26T13:40:18.09+00:00

Error code 2603 is related to network connection issues, specifically when the required endpoint 'odc.officeapps.live.com' cannot be reached. This can affect login and connected services with all Office applications, including Outlook. You'll need to configure your network, proxy, or firewall to allow all Office 365 required endpoints to resolve this.

Regarding the localhost call giving a 404-status code, this is typically a "Not Found" error, indicating that the requested resource could not be found on the server. This could be due to various reasons such as a mistyped URL, incorrect port number, or the resource not existing at the specified path. Please ensure that the server is running, the URL and port are correct, and that the route is properly defined in your application.

Share via

Login not working into desktop team app from external SAML identity