+16We have a HTTP connector flow, very simple GET toch check if a code exists. It uses basic authentication. The HTTP connector flow works. I added the same to a web connector with the base URL and basic authentication and the endpoints. The only difference is I get a 401 not authorized via de web connector but not via the HTTP connector.
There is no logging to debug further. How to proceed?
Best answer by Freddy
Hey Freddy,
That looks like that could be the issue yes. The Password field for Web connections is an nvarchar(100) whilst that for the HTTP connector is a varchar(4000). That makes the password of 128 characters a bit too long…
Sadly this cannot be part of a Platform improvement as this has major impact on the models and sf and IAM databases but we are able to restructure this in a upcoming version. Can you create a ticket for this to investigate and solve?
Created 9478S
+23Hi Freddy,
The functioning of basic authentication of the HTTP connector and the Web connector should not differ from each other. Are you sure both the username and password are the same for the connectors? If so, we would need to investigate further, please create a ticket for us with relevant information about the configuration so we can take a look.
+16Hi Freddy,
The functioning of basic authentication of the HTTP connector and the Web connector should not differ from each other. Are you sure both the username and password are the same for the connectors? If so, we would need to investigate further, please create a ticket for us with relevant information about the configuration so we can take a look.
Is there any chance the password field length is not the same?
the password is quite long, 128 characters.
+23Hey Freddy,
That looks like that could be the issue yes. The Password field for Web connections is an nvarchar(100) whilst that for the HTTP connector is a varchar(4000). That makes the password of 128 characters a bit too long…
Sadly this cannot be part of a Platform improvement as this has major impact on the models and sf and IAM databases but we are able to restructure this in a upcoming version. Can you create a ticket for this to investigate and solve?
+23What you can do is supply the password via a process variable for now. By setting the password field to {password}, then create an input parameter for the web connection, then in the Process action input map a process variable that holds the password.
+16Hey Freddy,
That looks like that could be the issue yes. The Password field for Web connections is an nvarchar(100) whilst that for the HTTP connector is a varchar(4000). That makes the password of 128 characters a bit too long…
Sadly this cannot be part of a Platform improvement as this has major impact on the models and sf and IAM databases but we are able to restructure this in a upcoming version. Can you create a ticket for this to investigate and solve?
Created 9478S
+16What you can do is supply the password via a process variable for now. By setting the password field to {password}, then create an input parameter for the web connection, then in the Process action input map a process variable that holds the password.
Thanks, but i'll stick with the HTTP connector for now, which works, and we'll switch on a later moment.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.