You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the user has no direct feedback when something is wrong with his template definition, instead only when the SecHub job starts/a PDS job starts, those jobs will fail and an error happens (because internally it is checked correctly inside scan domain and fail with a dedicated configuration failure exception).
But the user has no direct feedback and will only see that there was a technical/internal problem with the job.
Wanted
When a user defines template data we can have following situations:
no template defined by administrator -> not possible to handle
mandatory template variables are missing
additional/wrong template variable names are used
the validation setup of the template definition does not accept user input
When a job shall be created at scheduler an error shall be returned instead and job has to be created!
Solution
Inside the scheduler domain we check if at least one dataTemplate definition exists inside configuration (we use the existing resolver class for this).
If there is a template data setup found, the scheduler will send an event REQUEST_SECHUB_CONFIGURATION_VALIDATION . The scan domain will receive and handle the event.
as a result there will be a list of error messages (or none).
The event will be handled synchronous. If the error messages are not empty an exception with user info will happen. Also a dedicated HTTP error code (TBD) will be returned.
The go client shall be able to handle this accordingly (but this will be done in another issue)
The text was updated successfully, but these errors were encountered:
Situation
Currently the user has no direct feedback when something is wrong with his template definition, instead only when the SecHub job starts/a PDS job starts, those jobs will fail and an error happens (because internally it is checked correctly inside scan domain and fail with a dedicated configuration failure exception).
But the user has no direct feedback and will only see that there was a technical/internal problem with the job.
Wanted
When a user defines template data we can have following situations:
When a job shall be created at scheduler an error shall be returned instead and job has to be created!
Solution
Inside the scheduler domain we check if at least one dataTemplate definition exists inside configuration (we use the existing resolver class for this).
If there is a template data setup found, the scheduler will send an event REQUEST_SECHUB_CONFIGURATION_VALIDATION . The scan domain will receive and handle the event.
as a result there will be a list of error messages (or none).
The event will be handled synchronous. If the error messages are not empty an exception with user info will happen. Also a dedicated HTTP error code (TBD) will be returned.
The go client shall be able to handle this accordingly (but this will be done in another issue)
The text was updated successfully, but these errors were encountered: