Starts in:
2 DAYS
6 HRS
15 MIN
33 SEC
Starts in:
2 D
6 H
15 M
33 S

Activities of "serhatuysal"

Yes, you are right, I think localhost is sharing cookies (.aspnetcore.identity.application), When I open another browser, the problem does not occur. This is also an undesirable situation. Is there a way to solve this for us? Can we set a cookie for the application?

The problem with my SSO MVC example still persists. I sent the sample project to liming.ma@volosoft.com via wetransfer.

Another problem is as follows; I open two different empty applications (MVC UI) and run them without changing any settings. I cannot log in to both at the same time. When I log in to one, the session in the other application is terminated.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please first use the search on the homepage. Provide us with the following info:

  • ABP Framework version: v8.0.4
  • UI Type: MVC /
  • Database System: EF Core (SQL Server, .)
  • Tiered (for MVC) or Auth Server Separated (for Angular): yes/no

Hello, We have multiple Abp Client applications (MVC UI) and another Abp (MVC UI) project with our SSO application that is active with OpenIddict. We want the Client applications to log in through this SSO application, and we believe that we have configured everything correctly. However, we are facing an issue when running the Client and SSO applications. Here are the steps we are following:

  1. We log in to the SSO application as admin (admin - 1q2w3E*) at https://localhost:44353/account/login. (no problem)
  2. We open another tab and access the MVC application at https://localhost:44330. Then, we go to the login page and click on the OpenIddict external login button.(no problem)
  3. We are redirected back to the MVC application after logging in through SSO, where the SSO session was already active.(no problem)
  4. This is where the problem arises; During this process, the session in the SSO application is automatically terminated.
  5. When we try to log in to the SSO application again, we realize that the session in the MVC (client) application was also terminated unintentionally.

We have not been able to successfully integrate the SSO application into our application. Can you please help us identify where we might be making a mistake in the configuration of the SSO application?

If you want, I can prepare a simple sample pool and send it to you.

I'm sorry for my bad english

Showing 31 to 33 of 33 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06