Jump to content
We've recently updated our Privacy Statement, available here ×

Problem with iReport V3 and JS Plugin V3


Gaby38

Recommended Posts

Hello,

I post my problem on this forum after having posted it on Jasperserver forum.

Already, with jasperserver V2.1, I tries tu use ireport V3 and JS PLugin V3. It didn't work and to get it worrking I was obliged to overide jspluginV3 .jar by the V2 one in the lib directory of iReport. This was not shocking for me as I worked with a Jasperserver V2.

I migrated from JS V2 to JS V3 and I wanted to use the JS plugin V3 : I got the same error than previouly with the JS V2.

Tony on JS forum said me that he tested from a fresh install and it worked. On the same forum two other guys got the same kind of trouble with KS plugin V3.

To go further, I did wireshark captures of http traffic. Here after I paste the beginning of the content because I was not able to use the attachment fucntion of this new forum.

I quote the first part of th TCP stream. It's enough to see the difference.

For V3 plugin :



POST /jasperserver/services/repository HTTP/1.1Content-Type: text/xml; charset=utf-8
SOAPAction: ""User-Agent: Axis/1.4Host: mairie:8080Transfer-Encoding: chunked00
HTTP/1.1 401 Full authentication is required to access this resourceServer: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B49650; Path=/jasperserverWWW-Authenticate: Basic realm="Protected Area"Content-Type: text/html;charset=utf-8
Content-Length: 1130Date: Fri, 25 Jul 2008 17:41:34 GMT
<html><head><title>Apache Tomcat/6.0.16 - Rapport d'erreur</title><style>
<!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
 P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
 </head><body><h1>Etat HTTP 401 - Full authentication is required to access this resource</h1><HR size="1" noshade="noshade"><p><b>type</b> Rapport d'..tat</p><p><b>message</b> <u>
Full authentication is required to access this resource</u></p><p>
<b>description</b> <u>La requ..te n..cessite une authentification HTTP (Full authentication is required to access this resource).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.16</h3></body></html>POST /jasperserver/services/repository
 HTTP/1.1Content-Type: text/xml; charset=utf-8SOAPAction: ""User-Agent: Axis/1.4Transfer-Encoding: chunkedAuthorization: Basic amFzcGVyYWRtaW46cmFtYm8yHost: mairie:8080Cookie: JSESSIONID=CB168B4DDA7560D7990D950688B4965000
HTTP/1.1 501 Le m.thode 0    POST n'est pas d.finie dans la RFC 2068 et n'est pas support.e par l'API ServletServer: Apache-Coyote/1.1Content-Type: text/html;charset=utf-8

For V2 plugin :

POST /jasperserver/services/repository HTTP/1.0Content-Type: text/xml; charset=utf-8Accept: application/soap+xml, application/dime, multipart/related, text/*User-Agent: Axis/1.4Host: mairie:8080Cache-Control: no-cachePragma: no-cacheSOAPAction: ""Content-Length: 815Authorization: Basic amFzcGVyYWRtaW46cmFtYm8y<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:list soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://axis2.ws.jasperserver.jaspersoft.com"><requestXmlString xsi:type="xsd:string"><?xml version="1.0" encoding="UTF-8"?>
<request operationName="list" locale="fr">
.<resourceDescriptor name="" wsType="folder" uriString="/" isNew="false">
..<label><![CDATA[null]]></label>
.</resourceDescriptor>
</request>
</requestXmlString></ns1:list></soapenv:Body></soapenv:Envelope>HTTP/1.1 200 OKServer: Apache-Coyote/1.1Content-Type: text/xml;charset=utf-8Date: Fri, 25 Jul 2008 17:55:47 GMTConnection: close<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:listResponset

You can see that the authentication behaviour is not the same in the 2 cases (between the 2, only changed the V2 .jar of the plugin by the V3 one). In V2 the first http dialog sends the basic authentication string. In V3 it seems to do the authentication in two steps.

Is it normal or a bad work due to my context?

Thanks for your help

Link to comment
Share on other sites

  • 2 weeks later...
  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...