Component: OIDC v1.0.10
Issue: Error messages from custom user provisioning are lost in the authentication flow

Hi everyone,

I'm using the OIDC application for SSO implementation based on OpenID Connect. The application works perfectly - after simple configuration I had a working SSO solution.

However, during final implementation I've encountered an issue with error handling when using custom error pages and custom user provisioning.

Problem Description:

1. Custom_User_Check action: When an error occurs in my user provisioning logic, the error is properly returned via the ErrorMessage output variable.

2. DoLogin_Internal action: This action calls Custom_User_Check and correctly handles errors by adding the error message as a URL parameter to the custom error URL. This part works fine.

3. ParseCodeResponse action: This action calls DoLogin_Internal and has its own ErrorMessage output, but this is only used for initial code validation. When DoLogin_Internal returns an error, nothing is done with the RedirectURL or ErrorMessage - only the Success output variable is set to false.

4. Redirect endpoint: When DoLogin_Internal.Success is false, GetErrorPageURL is called to redirect to the error page. However, the error message and error URL with parameters from ParseCodeResponse are not available.

Result: Users are redirected to the error page but without any error message, making troubleshooting impossible.

Question: Is this a gap in the component's error handling flow, or am I missing something in the configuration/implementation?

It seems like the error message should be propagated up through ParseCodeResponse to be available when GetErrorPageURL is called.

Expected Behavior: Error messages from custom user provisioning should reach the error page so users can understand what went wrong.

Has anyone encountered this issue or found a workaround? Any insights would be appreciated.

Thanks!