Bug #233
login/password with extended character not working
| Status: | Closed | Start: | 11/05/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | patrick_elx | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Caller ID Superfectav 2.2.3 Maintenance Release |
Description
When a user enter a password with extended characters in the options (login or password) they are saved in an ISO superfecta database while entered in freepbx as UTF-8.
When sent back to the server, the credentials are not working.
History
Updated by patrick_elx 9 months ago
- Status changed from New to QA Testing
- % Done changed from 0 to 50
fix attempt in svn rev 233
Updated by patrick_elx 9 months ago
- % Done changed from 50 to 60
Updated by tshif 9 months ago
Who is working the QS for this? Should the case be assigned to that person?
Updated by patrick_elx 9 months ago
- Status changed from QA Testing to Assigned
- Assigned to set to patrick_elx
Updated by tshif 9 months ago
from pbxiaf forum user Krycek:
http://pbxinaflash.com/forum/showpost.php?p=36448&postcount=456
OK, I figured out what works. By default, FreePBX write this into the extensions_additional.conf file:
exten => cidlookup_1,1,Set(CALLERID=${CURL(http://maint:@password!@127.0.0.1:80/admin/modules/superfecta/bin/callerid.php?thenumber=${CALLERID})})
That doesn't work because of the "!" and the "", for obvious reasons. You can escape the "!", but the "" is used in that command, so you can't just escape it. The answer is to break out the username and pass from the URL, and escape the characters. I'm not sure how to modify the line to do this, but here is the curl command line it needs to pass:
curl -u maint:\@password\! http://localhost:80/admin/modules/superfecta/bin/callerid.php?thenumber=${CALLERID
Make sense?
Updated by patrick_elx 9 months ago
The special characters are now treated properly within superfecta (lookup sources, login/password for external sources).
However the main login/password in freepbx CID lookup still have this issue.
I have open a bug with freepbx as this problem is core related (http://www.freepbx.org/trac/ticket/3950#preview)
I would suggest to close this bug.