Andrew White
Andrew White
It means the application will set the tenant based on the claim in the cookie even if Identity later rejects the cookie during the authentication middleware. In practice this means...
Pages without authentication, in this case, would have the tenant set to whatever the claim was.
@HDScarpe Can you please open a new issue and provide a little more detail? What does your AddMultiTenant setup look like and how are your db context classes defined?
As the original issue was resolved in a prior release I'm going to close this item. Feel free to open new issues if needed.
Thanks @markgould I really appreciate it!
Just an update -- this is still in progress, but I'm still cutting public releases in the mean time.
I'm seeing this behavior too. ``` ➜ ~ echo "1234" | gpg -as - gpg: signing failed: No passphrase given -----BEGIN PGP MESSAGE----- gpg: signing failed: No passphrase given ➜...
Hi, one easy workaround is to stack the multitenant context in the `HttpContext` items collection during your request so that you can access it there after the normal multitenant context...
@natelaff glad to here from you. It's mainly a priority / time issue I think. The routing in Blazor as described [here](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.navigationmanager.locationchanged?view=aspnetcore-7.0) does have an event to hook into the...
Yes this is still active on the roadmap. I've done a few quick tests on this and the change impact is nontrivial on the code. Stay tuned.