Activities of "franciscosl"

When I take it to the production application, I am getting an error in this call: https://{0}.localhost:44393/.well-known/openid-configuration

The ports are different because it is another solution. What could be the reason for this?

Thank you. I am currently migrating the code to my production application, so I haven't been able to test it yet.

Reviewing the Nuget dependencies that I add to my application, I see that the Nuget Owl.TokenWildcardIssuerValidator is added, which comes from your personal repository,

Shouldn't this code be inside the abp code?

Now it works, I can access the new tenant via URL, but when I do so, the website is marked as unsafe.

Now I need to transfer it to my production application. Could you explain how you solved it and how everything works so that I can understand what I need to do, rather than just copying and pasting?

Thank you very much!

I get the following error:

error:invalid_request error_description:The specified 'redirect_uri' is not valid for this client application. error_uri:https://documentation.openiddict.com/errors/ID2043 culture:es ui-culture:es

I tried with a new database, and I get the same error. In both cases, I ran dbmigrator.

[maliming] said: hi

Reproducible repository: 👉 https://github.com/franciscosl-fnet/abp-app-domain-based

Can you share the steps?

I will check it

Thanks.

Hi, sorry, I thought that the problem description already explained how to reproduce it.

1. Start the host (DbMigrator previously runned)
2. Start Blazor
3. Create a new tenant from the host
4. Log out
5. Use the URL format described in the ticket to access the newly created tenant (using the local URLs)

Unfortunately, the proposed solution does not work for us. We have tested it both in our application and in a clean ABP application, and the behavior is the same.

To make this reproducible, I created a clean ABP 9.1.3 solution (Blazor Interactive – WebAssembly only) and applied the suggested changes.

Reproducible repository: 👉 https://github.com/franciscosl-fnet/abp-app-domain-based

In this sample:

• The tenant name is correctly extracted from the subdomain.
• However, the tenant context is not applied correctly, and the application does not work as expected.
• Same behavior in our real project and in this clean sample.

This suggests the issue is not project-specific. Any guidance after reviewing the repo would be appreciated.

Hello,

We believe that the problem comes from the support that ABP gives to blazor, because in other Blazor WASM applications published in azure this does not happen to us, we have no performance problems. Also, as we have seen in several links, this error is reported by several people, where they are also not given an effective solution.

The only solution is to have to migrate to blazor server or blazor webapp, is that the "support" given to blazor WASM?

You can try accessing other pages of the application the first time, some that do not make requests to the api, it takes the same.

Hello,

The error is that sometimes, most of the time, it takes more than a minute to access the application.

Sorry, but I'm missing the point of this thread.

1. You have asked about whether the cookie and the domain are on the same port.(https://abp.io/qa/questions/8623/3a17711b-c085-7e46-9c30-f1b7dd14075f).
2. After answering you that the cookie appears localhost without port you told me that I have two domains and that I can explain it to you.(https://abp.io/qa/questions/8623/3a17713f-4e4b-d3d1-0501-248f5f43d968).
3. I asked you what risks this entails and how I could change it, as I have not changed any of it, to which I received the reply of sending you the test project. Where you then asked me for a new abp project.
4. I implement a new solution and add two screenshots where you can see that exactly the same thing is happening.
5. I send you the project and your answer is that the api requests are correct, where in the gif you can't see the api headers and you can see that the cookie is "localhost".

I need to get the token so I can assign it to a request.