Activities of "berkansasmaz"

Hello, I used the information you provided to reproduce the problem. As a result, I added a middleware to the Blazor application as shown below. As you can see, I am able to access the access token, and the current user information is populated correctly. Could you clarify exactly where you are experiencing the issue?

OpenIdConnectOptions:

Hi Fabio.Zinesi,

Do you need it on client(Wasm) side or server side? Also, can you share the working version of AddMicrosoftIdentityWebApp's configuration?

Hello, sorry for the late reply. I will try your code during the day.

Hi,

Thank you for your question! I’m assuming you’re referring to integrating Microsoft’s authentication (likely via Microsoft Entra ID) as an external login provider using the Microsoft.Identity.Web library in your ABP Framework application. If you meant something else by "Microsoft Web Identity," could you please clarify? For now, I’ll provide some useful resource for Microsoft' s authentication:

• https://abp.io/community/articles/how-to-use-the-azure-active-directory-authentication-for-mvc-razor-page-applications-4603b9cf#gsc.tab=0
• https://abp.io/community/articles/how-to-setup-azure-active-directory-and-integrate-abp-angular-application-lyk87w5l
• https://abp.io/support/questions/7501/Problems-with-integration-of-Entra-External-ID
• https://abp.io/support/questions/8941/Switch-Azure-ADEntra-user-rather-than-pick-an-account-to-sign-out-of#answer-3a1897bc-1e1b-cc7a-726d-59cdb2761e65

The first resource I recommend is described using the Microsoft.Identity.Web NuGet package.

Hello Marcs 👋,

Sorry for the late reply, I missed this. We have a tutorial on modular monolith application development, you can complete it. Here is the tutorial: https://abp.io/docs/latest/tutorials/modular-crm

After completing it, you will learn how to add a new module to the host/final application, how to develop it, and how it communicates with other modules.

Best regards,
Berkan Şaşmaz
Developer Advocate https://www.berkansasmaz.com

Hello Sturla 👋,

I will open an internal discussion on this issue, and we will let you know the outcome here. Thank you for your understanding.

Best regards,
Berkan Şaşmaz
Developer Advocate https://www.berkansasmaz.com

I have assigned your issue to the relevant team member, and she will reply as soon as possible.

Hello Sturla,

Thank you for your feedback. I have created an issue regarding the problems you mentioned, and we will work on resolving them as soon as possible.

Best regards, Berkan

Hi,

Summary of the meeting

The customer is using the old microservice template and has configured dynamic proxy in their project. They can access all existing endpoints of the Identity Service without any issues. However, they are unable to access a newly added controller from the Web project.

Interestingly, when sending a request through the API Gateway, the controller responds correctly, which confirms that it is reachable. However, requests made directly from the Web project to this new controller fail.

I reviewed the gateway configurations and didn’t notice any issues. It appears that the problem is related to the Web project specifically.

Hello 👋,

We have upgraded the MongoDB Driver 2 to 3 in the new version, and we have prepared a migration guide for it. You can upgrade your application with minimal changes by following the migration guide.

Here is MongoDB driver 2 to 3 migration guide: https://abp.io/docs/latest/release-info/migration-guides/MongoDB-Driver-2-to-3

Unfortunately, there is nothing else we can suggest; this change is caused by MongoDB's driver.