Re-sign application and development manifest
Hi all,
is it possible to re-sign the application and deployment manifest of Report Builder? I found that the certificate signed by Microsoft has been expired which is causing trust prompt to end users. Thanks.
http://msdn.microsoft.com/en-us/library/dd465299.aspx
Rgds,
Zan
May 18th, 2012 3:28am
Hello Zan,
In Report Builder, credentials are often used when you connect to a report server or for data-related tasks, such as creating an embedded data source, running a dataset query, or previewing a report.
I recommend you that refer to the following article, it help you to understand credentials in Report Builder. Please see:
http://technet.microsoft.com/en-us/library/dd220515.aspx
Regards,
Bin Long
TechNet Subscriber Support
If you are TechNet Subscription user and have
any feedback on our support quality, please send your feedback here.Bin Long
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2012 5:32am
Hi Bin,
Thanks for your reply. Actually I'm not talking about how to authenticate against Reporting Server by using Report Builder, my problem is that the ClickOnce deployment manifest of Reportbuilder doesn't work when the trust prompt of the client workstation
is set to disable, which mean client failed to launch a Reportbuilder via Clickonce.
How to: Configure the ClickOnce Trust Prompt Behavior
Disable the trust prompt.
Disabled
The ClickOnce trust prompt is not displayed for any ClickOnce applications that are not signed with an explicitly trusted certificate.
http://msdn.microsoft.com/en-us/library/ee308453.aspx
After investigation, we found that the certificate used to signed the Deployment and application manifest of report builder has been expired. Is there any way to solve the issue? To set the trust prompt to either enabled or Authenticoderequired is not an
option due to company policy.
We consider re-signing the deployment manifest to replace the default one signed by Microsoft that should be able to solve the issue, but we have another concern that change may lead some violation
of Product User Right
any idea. thanks!
Rgds,
Zan
May 22nd, 2012 5:55am