Activities of "URITECHNOLOGY"

I'm trying to enable Data Protection following this tutorial https://aspnetzero.com/blog/persist-data-protection-keys-to-database. However, Data Protection is still using the FileSystemXml Repository instead of the database. Am I missing something? Is that tutorial up to date?

Thank you

-Rodolfo

Org Units appear to be duplicated when accessing the page as seen below. They are find and unique in the back end, but for some reason they are shown multiple times in the page. When interacting with the page, we noticed that they are setup the same in the html so when attempting to access child org units the page is very much buggy as it closes or opens at whims. Please advise.

This solution is not an angurlar version. We're using memory cache, no replacements have been done to this logic at all. It is however, load balanced on two iis servers, could that be causing an issue? I will make sure to email you the logs ASAP.

Thank you for the quick response!

Prerequisites

Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• What is your product version? v8.2.1
• What is your product type (Angular or MVC)? MVC
• What is product framework type (.net framework or .net core)? .net core

If issue related with ABP Framework

• What is ABP Framework version? .NET Core 3.1

If issue is about UI

• Which theme are you using? Default
• What are the theme settings? Default

We're having issues impersonating users in our system. It's not a consistant bug as some users can and some cannot, it may even be a browser issue. Just want to see if anyone has encountered it or has resolved it in some way or another.

It would be great to have some one from the support team comment on this to ensure that this is the fix before we deploy.

https://support.aspnetzero.com/QA/Questions/8783/Login-Loop---Chrome-Fails---IE-Working---Hosted-In-IIS

@marble68 Above is the fix.

           var cookieOptions = new CookiePolicyOptions
            {
                MinimumSameSitePolicy = SameSiteMode.None
            };
            app.UseCookiePolicy(cookieOptions);

If you apply the above code with and use a self-signed SSL cert for local development, it will work and impersonation will also work.

Internally it is calling the authentication controller using http which is breaking in chrome.

We manually set the cookie to https to bypass the strict, but its breaking the impersonation functionality because it is persisting through the session..

Below is what we are using to bypass the Strict policy set by Google Chrome

           var cookieOptions = new CookiePolicyOptions
            {
                MinimumSameSitePolicy = SameSiteMode.None
            };
            app.UseCookiePolicy(cookieOptions);

We need an example of how to set the cookie properly or figure out a configuration setting to redeploy the app using Chrome 80+.

All of our apps have been configured with HTTPS and strict secure.

This seems to be on a User profile basis. I can log on to another profile in windows and open chrome to complete auth.

We are seeing a 302 (redirect) response to /App so it is posting.

We have made zero changes to Authentication.

@marble68

We are using JQ 8.9. It is redirecting to %2fApp. We are not using MFA or two factor.

It is not logging all the way in, no .AspNetCore.Identity.Application Cookie is set.

Only when that file named "Local State" is regenerated will it complete the log in.

One of the objects in the file (hard to tell which one exactly) is probably persisting the session token from before the update.