[ 
https://issues.apache.org/jira/browse/CONNECTORS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453858#comment-13453858
 ] 

Maciej Lizewski commented on CONNECTORS-518:
--------------------------------------------

There is one problem (when I look at your changes).
According to http://www.mediawiki.org/wiki/API:Login. Token confiramtion (two 
step login) does not apply to all cases:

Confirm token
If the response to the above query was Success instead of NeedToken, you can 
skip this step. (This extra step was added in MediaWiki 1.15.3.) In MediaWiki 
1.15.4, first phase of login in ApiLogin.php is broken, so login/sessionid 
parameter is not returned, thus token confirmation is impossible. Apply 
ApiLogin.php file from MediaWiki 1.15.5 to your installation as a quick 
workaround while you plan your upgrade to 1.15.5. ApiLogin.php from MediaWiki 
1.16+ is incompatible with MediaWiki 1.15.3+.

so forcing Connector to throw exception when first step does not return token 
is not always right...

there is also something wrong with getting documents to index. seems like it is 
hanging in infinite loop when fetching document list:

192.168.1.1 - - [12/Sep/2012:11:19:57 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=Tutorial+Install+%28CRM+%2FIntranet%29&aplimit=500
 HTTP/1.1" 200 5944 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:19:57 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=%C2%8Crodowisko+Developerskie+VirtualBox&aplimit=500
 HTTP/1.1" 200 445 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:19:57 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=&aplimit=500 HTTP/1.1" 
200 29174 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:19:59 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=Korzystanie+z+komputerow&aplimit=500
 HTTP/1.1" 200 28682 "-" "Jakarta Commons-HttpClient/3.1"

and again...

192.168.1.1 - - [12/Sep/2012:11:20:00 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=Tutorial+Install+%28CRM+%2FIntranet%29&aplimit=500
 HTTP/1.1" 200 5944 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:20:00 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=%C2%8Crodowisko+Developerskie+VirtualBox&aplimit=500
 HTTP/1.1" 200 445 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:20:00 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=&aplimit=500 HTTP/1.1" 
200 29174 "-" "Jakarta Commons-HttpClient/3.1"
192.168.1.1 - - [12/Sep/2012:11:20:02 +0200] "GET 
/api.php?format=xml&action=query&list=allpages&apfrom=Korzystanie+z+komputerow&aplimit=500
 HTTP/1.1" 200 28682 "-" "Jakarta Commons-HttpClient/3.1"

ans so on... the job in manifold panel shows 'Starting up', and Documents and 
Active counts reach proper number and does not change. So it seems that logging 
in and fetching list works but the process does not advance to index documents.
                
> Wiki Connector support for API authorization and security tokens
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-518
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-518
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Wiki connector
>    Affects Versions: ManifoldCF 0.6
>            Reporter: Maciej Lizewski
>            Assignee: Karl Wright
>             Fix For: ManifoldCF next
>
>         Attachments: WikiConnector.java, wiki.zip
>
>
> Wiki connector does not support API with restricted access (there is "login" 
> method in API: https://www.mediawiki.org/wiki/API:Login)
> There is no "security" tab for forced authorization tokens or any other 
> security implemented. There should be at least forced tokens tab or tokens 
> assigned to wiki namespaces (second would be better)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to