Put auth token in /url/PATH

Right, it won't do that :(

It can submit as ?param=values
Or as a JSON post.

Should the received token be passed manually into import request URL? I thought, somehow the module store and append it automatically to the request url.
I don't seem to get anywhere close to understand how this work. Here is my setting

Authentication format--------
use plain

credentials--------
user|username
pass|password
other_param|other_value

2 step auth
Yes

Feed Login URL--------
https://example.com/login?user=username&pass=password Here I should add other_param?other_value but the input field is not allowing. Seems like there is a limit on the field

Authentication response fields (token names)--------
access_token|utoken

Request url----------
https://example.com/request

response-----
It's failed with 401 unauthenticated request

When tried with postman, I can see successful result with as follow
authentication------
https://example.com/login?user=username&pass=password&other_param?other_...
Response--------
access_token: "some_taken"
Request------
https://example.com/request?utoken=some_taken
response----
successful feed content

Any idea on the right settings or what I'm missing?

Hi PoidsTotal:

It's been a while since I've been in the code, but it seems like you would not put any parameters in here:
Feed Login URL.

Where you said:

https://example.com/login?user=username&pass=password Here I should add other_param?other_value but the input field is not allowing. Seems like there is a limit on the field

Try just: https://example.com/login
and see if that works.

Well, I just looked at the screenshot and seems maybe I'm wrong.
Seems the "Authentication credentials" would only be for JSON post authentications.

You can right-click and inspect the Feed URL field to see if it is setting an input limit.

@drastik
Sorry, strangely I didn't get your response notification. To get back to the issue... Yes there is "maxlength="128"" in the login field. it should be fine for most usage but my params are particularly long.
Change to simple use https://example.com/login and JSON format is resulting in the same error...
The problem is either the login request failed or the token has not been retrieved. In any case, the error returned the request url without an appended token