issue with blank pages with callbackpath
hi there,

i am using the auth0 authentication api (v5.10.0) on the .net core 2.1 platform, with a similar configuration offered in the quick-start guide. our landing page has a login button that uses auth0 lock to provide the login form.

the authentication works great when it is used as intended, …
this is because the /login page, once a login occurs, the ‘state’ parameter is missing and so when the page tries to call the /authorize url it will error. the state parameter is used to mitigate csrf attack and so during authentication, the application sends this parameter in the authorization …
We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: I have now implemented the following solution.


As CodeNotFound pointed out in the comments, IdentityUser used to have a `Roles` property. This is no longer the case in .NET Core. This [comment/issue](https://github.com/aspnet/Identity/issues/1361#issuecomment-348863959) on GitHub seems to be the current solution for .Net Core. I have attempted to implemented it with the following code:


**ApplicationUser**



```
public class ApplicationUser : IdentityUser
{
    public ICollection<ApplicationUserRole> UserRoles { get; set; }
}

```

**ApplicationUserRole**



```
public class ApplicationUserRole : IdentityUserRole<string>
{
    public virtual ApplicationUser User { get; set; }
    public virtual ApplicationRole Role { get; set; }
}

```

**ApplicationRole**



```
public class ApplicationRole : IdentityRole
{
    public ICollection<ApplicationUserRole> UserRoles { get; set; }
}

```

**DBContext**



```
public class ApplicationDbContext
    : IdentityDbContext<ApplicationUser, ApplicationRole, string, IdentityUserClaim<string>,
    ApplicationUserRole, IdentityUserLogin<string>,
    IdentityRoleClaim<string>, IdentityUserToken<string>>
{
    public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
        : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder);

        builder.Entity<ApplicationUserRole>(userRole =>
        {
            userRole.HasKey(ur => new { ur.UserId, ur.RoleId });

            userRole.HasOne(ur => ur.Role)
                .WithMany(r => r.UserRoles)
                .HasForeignKey(ur => ur.RoleId)
                .IsRequired();

            userRole.HasOne(ur => ur.User)
                .WithMany(r => r.UserRoles)
                .HasForeignKey(ur => ur.UserId)
                .IsRequired();
        });
    }
}

```

**Startup**



```
services.AddIdentity<ApplicationUser, ApplicationRole>(options => options.Stores.MaxLengthForKeys = 128)
            .AddEntityFrameworkStores<ApplicationDbContext>()
            .AddDefaultTokenProviders();

```

Finally, make sure when you're using it that you eagerly load the User's UserRoles, and then the UserRole's Role like so:



```
this.Users = userManager.Users.Include(u => u.UserRoles).ThenInclude(ur => ur.Role).ToList();

```

I had an issue where the `Role` property of each `UserRole` was null and this was resolved by adding in the `.ThenInclude(ur => ur.Role)` part.


Microsoft doc on multi-level eager loading: <https://docs.microsoft.com/en-us/ef/core/querying/related-data#including-multiple-levels> i seem to have fixed this by myself. i disabled probe on my .vcl and this seemed to fix the 503 issues. here is my .vcl for varnish incase anyone needs it(this might work for you)! :slight\_smile:

vcl 4.0;

backend default {

.host = "127.0.0.1";

.port = "81";

.connect\_timeout = 5s;

.… hi, 
  
we did try following: 
  
1. update java to the latest version 
this didn't affect the cpu or ram consumption. 
  
2. assign more ram for java, we found on other forums that high pcu consumption was caused by lack of memory. 
this didn't affect the cpu consumption neither 
  
3. change the port for connector from 8443 to to save resources for port redirection. 
the cpu consumption for the redirection is so low that it didn't change either 
  
4. try to disable autodeploy and do it manually 
we couldn't do this as the concerned era is allready in production 
  
5. do you have issues with http traffic as well or just with https? 
as we are working on security, there is just no http at all ! (disabled in tomcat) 
  
  
but we found out that regarding the place from which we did connect (and the available bandwith) it did impact the behavior. 
whith a good bandwith: the page loads in something as 10 to 15 seconds and cpu load doesn't go at 100% or just for the few last seconds 
whith a bad bandwith: the page takes 1 to 3 minutes to load and cpu consumption goes to 100% (over several cores) after the 10 first seconds (just like a memory leak but with cpu). 
  
we don't get why but the longer it takes for the client's side (browser) to load the app, how more cpu is consumes on server... after updating to home assistant core 0.107.5 this issues seems to have resolved. it’s been working properly for a few days now. was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . hi yerhu,

i could imagine, that one of the two following scenarios may cause the issue:

you’re using an outdated version of tk-core. check in your configuration: core/core\_api.yml

you’re using a pipelineconfiguration, which is pointing to a local-path and includes a file like python\_interpreter, i… hi,

do you have joy package installed with all necessary packages/dependencies ?

try to search for joy\_node or run joy package examples to find out what is going wrong. I suppose you could try overriding the encoding in the `HtmlWeb` object.


Try this:



```
var web = new HtmlWeb
{
    AutoDetectEncoding = false,
    OverrideEncoding = myEncoding,
};
var doc = web.Load(myUrl);

```

Note: It appears that the `OverrideEncoding` property was added to HTML agility pack in revision 76610 so it is not available in the current release v1.4 (66017). The next best thing to do would be to read the page manually with the encodings overridden.