Closed chirino closed 7 years ago
I had left the refresh token field empty. We can get around the issue if you enter a value into the refresh token field, and then erase it. Seems that avoid sending a null value for that field to the backend.
Was able to create one here against staging without having to enter anything into the form. Looking at the form config in the network tab, all the fields are required: false
, if that's not the case then they should be set to required: true
, which should (hopefully) disable the Next button until the required fields are entered in.
So I think the issue was that the config map was sent with a null value. I inspected the request in the chrome debugger. You think that's not possible?
Yeah, managed to reproduce it here, there's a couple issues. The error I get back is kinda meaningless to me:
developerMsg
:
"Internal Server Exception. configuredProperties value↵ at [Source: io.undertow.servlet.spec.ServletInputStreamImpl@2a7eeded; line: 131, column: 3] (through reference chain: com.redhat.ipaas.model.connection.Connection$Builder["configuredProperties"])"
errorCode
:
500
userMsg
:
"Please contact the administrator and file a bug report"
If it's the case that these values should be set then they should be set to required: true
, and if not, then the backend needs to ignore the null value really.
I'll see if I can strip those out before sending, maybe that'll sort it.
I think if they have null values you should not include them in the map. since they are not required.
Linked PR seems to do the trick for me...