Hi
We have been trying to update to version 6.0 from 5.3.4 and are having issues getting the login to work for Blazor WASM.
As stated here our CMS is in the IdentiyServer project.
We get a unhandled 400 error like this (only in Azure.. works locally)
We have a ExceptionSubscriber in the IdentiyServer project but we don´t get anything there.
We can log into our MVC public page, no problem.
I just saw the following error message in the console while the Blazor was loading up that could be the cause.
Refused to display in a frame because it se 'X-Frame-Option' to 'sameorigin' What do you think and how should we fix it?
- ABP Framework version: v6.0.0
- UI type: Blazor
- DB provider: EF Core
- Identity Server Separated: yes
3 Answer(s)
-
0
The only error it is throwing is there is not strack trace just this message
[ERR] Unhandled exception! System.Exception: Unhandled exception!We have also attached certificates
-
0
Here we have some extra information in the logs.
Could some CMS file be missing that is causing this error? Note that we have our CMS located in the IdentiService and not the public website.
And btw we have this
ExceptionSubscriberin the IdentiService that only catches this unhandled exception with no details at all.public class OurExceptionSubscriber : ExceptionSubscriber { private readonly ILogger<OurExceptionSubscriber > logger; public OurExceptionSubscriber (ILogger<OurExceptionSubscriber > logger) { this.logger = logger; } public async override Task HandleAsync(ExceptionNotificationContext context) { logger.LogException(context.Exception); logger.LogError(context.Exception.StackTrace); logger.LogError(context.Exception.Source); logger.LogException(context.Exception.InnerException); } } -
0
this is reproducable when you add more uri to redirect uri and post logout uri for blazor .
