Hello, thank you for reporting this. We will be fixing the problem as soon as possible and refunding your ticket.
Hello, we have not made any change that would affect here. My question is whether you have customized any part that might suppress here since I cannot produce the same problem on my side.
Ah, that makes complete sense. Thank you!
I wonder, though: is there any ability to highlight the menu item for child routes? As in my example, we usually have /list and /detail child routes. It would be nice to be able to set a menu item "Page 1" with a path of "/module1/page1" and have it be marked as active if we're at either "/module1/page1/list" or "/module1/page1/detail".
Hello, you can manage the breadcrumb value by adding the breadcrumbText
attribute to your route configurations like this
{
path: '/module1/page1',
name: 'M1P1',
parentName: '::Menu:Module1',
order: 1,
iconClass: 'fas fa-table',
layout: eLayoutType.application,
breadcrumbText: 'Custom Breadcrumb',
}
However, the highlight you mentioned is also managed within this route config for the time being. So, you will need to add them here.
Thank you for providing the related screenshot, and I will consult my teammates about this problem. I also see that you have been using the old CLI for managing this action, so I can suggest you to use the new one until then https://abp.io/docs/latest/cli/differences-between-old-and-new-cli
Thank you for providing more details. As mentioned in the documentation, you can specify the version for this case https://abp.io/docs/latest/CLI#get-source
This part should be working the same for the cli as well. Can you please share the related package.json that has been generated for the gdpr project? May I also know your cli version?
Hello, this part has been refactored and fixed in the next version being 9.0 with this PR https://github.com/abpframework/abp/pull/21197
Thank you for providing more details on this. However, I am unable to produce the same problem with a project created by using this command abp new MyTestApp -t app -u angular -csf
. May I know whether you have made a related change or come across another problem and produced such problem?
Thank you for your patience, and I apologize for the delayed response. This problem has been fixed and will be available for the next version. May I know whether you get the same error even if you use the --legacy-peer-deps
option?
Thank you for your patience, and I apologize for the delayed response. I have carefully revisited your concern in light of the latest updates. Based on the analysis, the logs and debugs are not triggered as the errors in question are likely occurring earlier in the process.
Here is a detailed explanation of the issue:
400 Bad Request
Error:
This error indicates that the request to the identity provider (IdP) was unsuccessful. Common causes include:
When this error occurs, the OpenID Connect library is unable to complete the authentication flow, leading to a secondary error.
Recommended Approach:
To achieve a clearer response from the library, consider reviewing the discussion here and implementing the solution described in this sample project.
invalid_nonce_in_state
Error:
As illustrated in the attached example, this secondary error occurs when the library detects an incomplete or invalid flow and securely terminates it to prevent further processing with incorrect or missing information.
This behavior is by design and serves as a safeguard, ensuring that broken authentication attempts are securely halted. It is not indicative of a bug, but rather a critical feature to maintain security. However, this may have downstream impacts on your business logic, so adjustments might be necessary to account for this scenario.