EAIF VASP - "User Not Defined" log entry

EAIF VASP - "User Not Defined" log entry SearchSearch
Author Message
Darren Elwood
Unregistered guest
Posted on Tuesday, October 21, 2003 - 04:41 pm:   

Hi,

I've configured an EAIF VASP account (with name as the submitting IP address 10.11.12.13) and I'm posting a valid EAIF message through the interface to path "/eaif".

Getting an error in the MMSC-<DATESTAMP> log file:

2003-10-21 16:22:11,MMSIN,10.11.12.13,HTTP/1.1,,User Not Defined, FAILED

The HTTP POST does not specify a username or password in the URL.

All sender and recipient addressing is in the EAIF payload rather than http headers and is specified as international format phone numbers "+44..../TYPE=PLMN" (each of which is registered unders [MMSC Users] config tab).

Any ideas what would cause this error message?

Many Thanks,
Darren
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 942
Registered: 10-2002
Posted on Tuesday, October 21, 2003 - 07:16 pm:   

Darren,

Can I see the complete HTTP header of your POST?

You need to either include an "Authorization:" header (with base64 encoded username:password) ... or you need to define the IP address of the workstation performing the submit as a VASP account.
Darren Elwood
Unregistered guest
Posted on Wednesday, October 22, 2003 - 09:50 am:   

Hi Bryce, thanks for your response.

I've set the VASP account name as the IP address of the submitting workstation.

Here's the http post header:

POST /eaif HTTP/1.1\r\n
Connection: close\r\n
Host: 10.11.12.14:80\r\n
User-Agent: libwww-perl/5.63\r\n
Content-Length: 460\r\n
Content-Type: application/vnd.wap.mms-message\r\n
X-Nokia-Mmsc-Message-Id: JAB-AApMAQQAACnJAAAAAwAAAA8AAAAA\r\n
\r\n

Thanks,
Darren
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 950
Registered: 10-2002
Posted on Wednesday, October 22, 2003 - 08:11 pm:   

Darren,

Sigh. This is a definite bug. It looks like the EAIF interface is not properly accepting connections where the account name is an IP address.

Is it possible for you to change the account name, and then POST to a URL of /eaif/username=password instead?

(You can still use IP address restrictions on the account to limit the IP addresses from which this account can connect.)

-bn
Darren Elwood
Unregistered guest
Posted on Friday, October 24, 2003 - 01:57 pm:   

Hi Bryce,

Yes I can change the submitted URL to include username=password.

Do you want any config etc forwarded for bug resolution purposes?

Regards,
Darren
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 977
Registered: 10-2002
Posted on Tuesday, October 28, 2003 - 03:20 pm:   

Darren,

No need for additional information. This one was easily enough recreated when we tried it.

There seemed to be a URL parsing problem ...

If the URL was "/eaif", then the parser would think the "HTTP/1.x" string was the user name. If the URL was "/eaif/", or "/eaif/username=password", then the parser would work properly.

We've got a fix for the next for this in the next patch.

Thanks!