Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "alexanderpilhar"

Have a look at this one (might be the same): [exception when impersonating tenant user #8611](https://support.aspnetzero.com/QA/Questions/8611)

8.7.0, Core, Angular

In Web.Host\Startup\Startup.cs we can see the following line: services.AddSignalR(options => { options.EnableDetailedErrors = true; });

This is what Microsoft Docs say about EnableDetailedErrors:

If true, detailed exception messages are returned to clients when an exception is thrown in a Hub method. The default is false, as these exception messages can contain sensitive information.

So, you might not want to have EnableDetailedErrors turned on in an production environment. I guess, this might have been forgotten to be disabled after debugging some SignalR stuff?

Hi @ismcagdas and thank you for your answer!

Yes, I'm already working on an implementation - I was just wondering if people where using other solutions for taxation ... maybe PayPal or Stripe offer something that is easy to use!?

Anyway, closing this now!

8.2.1, Angular, .Net Core

This is a general question about selling a product / service built with ASPNETZERO and the implications when it comes to invoicing and taxation / taxing.

Let's assume the following:

  • company's home is a country in the European Union (EU)
  • product / service will be available international
  • product / service will be available for B2B and B2C

Invoicing and taxation / taxing is depending on:

  • Where the tenant is from (same country / member of the EU / outside EU)
  • The type of tenant (B2B / B2C)

As far as I see, there is no built-in way in ASPNETZERO to handle this scenario yet. So, how do you do it?

@maliming thank you for this information about cancellation-tokens!

Still, I wonder why I see an exception in my dev environment (in Visual Studio IDE, not in Logs.txt) since 8.2.1 ...

Anyway, thank your very much for your time @maliming!

@maliming actually, the exception doesn't seem to affect the application anywhere but in my development environment - and there I can simply click continue. Nothing bad seems to happen.

I already have it in production but I can't tell if it occurs there as well, since I don't have logs working in production environment yet (IIS, self hosted). It seems the application just continues to work as well.

So, yes, you are right - it might not affect the application in any bad way. But, should I remove the suggested code or should I keep it (I guess, you just wanted me to test something, right)?

@maliming where do i have to place this code? PreInitialize() of which module?

EDIT:

I placed it at the end of PreInitialize() in core-module - the exception is gone!

But what does it mean? Is this the solution you suggest? Are there any other implications with this? Or will this work fine?

@maliming no, the request has not been canceled.

FYI: After login, I'm not routing to the dashboard that comes with ASPNETZERO but to a custom component (which is a default feature but also needs permission) - could this have something to do with the exception thrown?

The exception also occurs when selecting another user of a specific tenant for impersonation, e.g.:

  • Impersonate tenant A user A.1 => exception
  • Impersonate tenant A user A.2 => exception
  • Impersonate tenant A user A.1 again => no exception
  • Impersonate tenant A user A.2 again => no exception

@maliming sorry, I can't tell for sure. If the process of impersonation involves a logout ... I just can't tell.

But heres another Log.txt that involves the following:

  • Login as host user
  • Logout
  • Login as host user
  • Impersonate tenant A user A.1 => exception
  • Back to host user
  • Impersonate tenant A user A.1 again => no exception
  • Back to host user
  • Impersonate tenant B user B.1 => exception
  • Back to host user
  • Impersonate tenant C user C.1 => exception
  • Back to host user
  • Impersonate tenant B user B.1 => no exception
  • Back to host user
  • Impersonate tenant C user C.1 => no exception
  • Back to host user
  • Impersonate tenant A user A.1 => no exception
  • Back to host user
  • Logout

Log.txt: 20200303-Log.txt

Showing 71 to 80 of 224 entries