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.
Hello again. If you mean that the navbar cannot be pinned for the 1200px, the expected behavior is not satisfied. Normally, it should be pinned if the size is 1200px and wider, and open on hover if the width is less. But, it seems working in both cases.
I have also checked on different browsers such as Safari, Opera and Firefox. If you are getting this error for another browser type, I can assist further.
Hello, we weren’t able to resolve the issue just yet, but it is on track to be fixed by the end of the next release. Thank you for your patience, and apologies for the wait.
This fix will be released by the next patch version for 8.X.X. Thank you for your cooperation.
As mentioned earlier, the approach will depend on your specific business needs. Here are two options you can follow to customize the relevant sections. If your goal is simply to hide certain elements, you can achieve this easily by overriding them with CSS properties.
As an alternative, you can use the npm-force-resolutions tool to temporarily address these dependency issues. This solution allows us to enforce specific versions and maintain stability in the short term. Rest assured, we’re actively working on a more permanent fix, which will be included in the upcoming release.
Hello, this component is not directly replaceable. You can either try to customize the root component that has the eAccountComponents.PersonalSettings , or customize the form using the extension system based on your requirements.
I am still unable to replicate the issue on my end.
Thank you for providing extra details. For the best stability, we recommend using Yarn for managing dependencies, as it handles compatibility more smoothly. However, if switching to Yarn isn’t possible, adding the --legacy-peer-deps flag to NPM can also maintain stability by bypassing certain version checks. Our priority is to keep your application stable and reliable, so please let us know which approach works best for you.
Thank you for sharing additional details. I was able to achieve a successful build without any issues, which leads me to believe this may be related to specific customizations in your setup. Could you provide us with a sample project to help us investigate further? Please feel free to reach out via email at sumeyye.kurtulus@volosoft.com.
