Need help regarding password encryption in the report(URGENT, PLEASE) [message #119441] |
Sun, 29 January 2006 22:49  |
Eclipse User |
|
|
|
hi all,
Iam using birt2.0M3 Report engine for report generation.I have deployed
report engine in jboss4.0.3 server. Now we are giving options to user to
upload a template and generated a report through the browser.
After uploading, we are parsing the design file and giving options to
user to change the database information. After user has changed the his
desired database information we are updating this information in the
design file through DOM parser.
In the design file password is in encrypted format. So we need to place
the new password in the encrpyted format only. Can any one help me how to
do this encrytion. What is the birt api for encryting the user entered
password.
It is very urgent, please help me.
Regards,
Bhaskar.
|
|
|
|
|
|
|
|
|
Re: Need help regarding password encryption in the report(URGENT, PLEASE) [message #124133 is a reply to message #124096] |
Fri, 03 February 2006 14:50  |
Eclipse User |
|
|
|
Thanks for the info Scott, this is a very good starting point.
Brian
Scott Rosenbaum wrote:
> Brian,
>
> This is fairly basic but you could try:
> http://www.eclipse.org/birt/phoenix/deploy/designEngineAPI.p hp
>
> Also if you look through the newsgroup, I believe there are a number of
> additional examples.
>
> Scott Rosenbaum
> BIRT PMC
>
> Brian Kallay wrote:
>
>> Hi Gary,
>>
>> Are there any examples for the Design Engine API that I can look at to
>> get started? I am currently updating the xml using JDOM but as you
>> pointed out this could be problematic if there are schema changes so I
>> would like to start using the API instead.
>>
>> thanks,
>> Brian
>>
>>
>> Gary Xue wrote:
>>
>>> Is it possible for you to use BIRT Design Engine API to update the
>>> report
>>> design, instead of modifying the XML directly? This is your best choice
>>> since DE API is a rich abstraction layer above the report design XML. It
>>> insulates you from future schema change, and offers features like
>>> encryption
>>> and validation.
>>>
>>> Alternately you can externalize the DB password to store it outside
>>> of the
>>> report design. I have some previous posts on this topic in this
>>> newsgroup on
>>> how to do this.
>>>
>>> It may also be possible to write your own encryption extension to supply
>>> your own encyption code. I will try to some information on how to do
>>> this
>>> and post a note later.
>>>
>>> regards,
>>>
>>>
|
|
|
Powered by
FUDForum. Page generated in 0.03896 seconds