Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of hendriksusanto1981@gmail.com
 designates 72.14.204.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=CEIRKIIo15FWd5+MS2pm1616BZ3xonJFpePAKR1vwK3WulbZUVOX1iiP4UTwRIUe3g
         qIXxFsDC+vzaSysvqjQ1YEry7K6Lm5NgPmviVk+zrktLhlqDbsWU8ntX51bizDNjGt5o
         dC35qC4xFVWvzHYpk+GxmoVFxgag2yjmFzShs=
MIME-Version: 1.0
Date: Mon, 2 Feb 2009 14:30:47 +0700
Message-ID: <3944d72a0902012330i5129485fw264443ddc6e427@mail.gmail.com>
Subject: using windows authentication through JDTS on BIRT on TOMCAT
From: hendrik susanto <hendriksusanto1981@gmail.com>
To: users@tomcat.apache.org
Content-Type: multipart/alternative; boundary=000e0cd2dc408353f70461ea88ca

--000e0cd2dc408353f70461ea88ca
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi, I'm newbie with tomcat,

Can somebody help me solving my problem? I really apprciate it, cause it has
made me frustated

Currently I'm working with BIRT, tomcat and MSSQL

I use BIRT to create report as an add-on to our ERP. We tried to using
windows authentication as SSO in all the report, so the roles is described
in MSSQL security and the report's security just based on security from
MSSQL. I'm using JTDS as JDBC Driver because it can integrate Windows
Authentication

When I design the report, the driver works well, so I could using MSSQL
roles as security in my report, for example when I set the "domain\user" can
access view "stock", so in the report the user can access the view, when I
set the user cannot access or execute the view or stored procedure in MSSQL,
so the report cannot retrieve the data. In RCP design all work fine.

But when I copy the report to tomcat webapps, the driver doesn't work. The
error logs said that it couldn't authenticate the domain\user against the
MSSQL. so the connection cannot be open

Does anyone can help me for this problem?

Thanks in advance
Hendrik

--000e0cd2dc408353f70461ea88ca--