User1573524638714754949 (Customer) asked a question.
We are trying to implement a new workflow to customize the SAML Assertion generated for an application. Unfortunately, Okta is processing the originally generated SAML assertion if Inline Hook fails.
From Okta Documentation -
"If a response to the SAML assertion inline hook request is not received from your external service within 3 seconds, a timeout occurs. In this scenario, the Okta process flow continues with the original SAML assertion returned."
Note: Okta is processing the originally generated SAML assertion to the application even if we send any status code other than 200 to as the response.
Is there any chance to stop the workflow and load an error message/page to the user?
Thanks,
@User1573524638714754949 (Customer) - Short answer: No.
Workflows or any other "endpoint" you are using to perform the payload processing from the inline hook is only going to receive the payload from inline hooks (regardless of the inline hook type). It is then listening for default (3 seconds) for a response. If no valid response is made within the timeout period it defaults to using the original value and does not provide any sort of response back to the payload destination (the place processing the data). Think of it sort of like how UDP works instead of TCP.
What you are asking about is not technologically possible with the feature design.