We are using bearer token to authenticate APIs in WebReportDesignerController, however for WebDesignerHandlerController, bearer token option does not exist in WindowsClientWebDesignerConfig.AuthenticationMode. How can we use the same bearer token that we use for APIs in WebReportDesignerController, also in WebDesignerHandlerController APIs.
Would it be sufficient to copy the Authorization header from the request for the DesignerLauncher? Or would you need a way to pass the header seperately?
Yes, copying the Authorization header from the API that start the Designer will be sufficient. I hope this header will be used in all further API calls from Designer.
Yes, the latest SP has the changes required. It would be very helpful if you could test them in advance to make sure they meet your requirements. We are currently planning a service pack release by mid-January.
I have tested with AuthorizationHeader option. WebDesigner launch API succeeded but “ListLabelWebDesigner/WebDesignerHandler/CheckDesignerIsStarted“ failed with 401 Unauthorized response. Looking into the script returned by Initiator API, the “ajaxCall“ method used is not adding any headers to the API call. Hence it will fail. Can you have a look here?
We were able to reproduce this issue - a new release that should tackle this is available by tomorrow, again via the “Latest Prerelease Service Pack”. Thanks for your input!
I have tried with the latest Service Pack. While the issue with “CheckDesignerIsStarted“ is fixed, the call to /WebDesignerHandler/DownloadDesigner fails with 401 response. I could not find the Authorization header in this API request. Can you check this?
We are still working on this matter and unfortunately cannot offer anything at the moment. We hope to provide more information next week and will keep you informed.
Thank you for your patience and please accept my apologies for the delay. This morning, we made another internal adjustment regarding this matter. An updated Latest Prerelease Service Pack will be available starting tomorrow, and we would appreciate your feedback.
Thanks for the fixes and its working in most cases except during Preview operation in WebReportDesigner. Following API is called with bearer token in the URL and not as header. Can you please have a look.
Thank you for your test and the positive feedback regarding it.
I have already forwarded the open issue concerning the preview in the Web Report Designer to the development department for a detailed review. I will inform you as soon as I have any updates. Thank you for your patience.
Thank you for your message, and I wish you a Happy New Year.
Over the past two weeks during Christmas and the New Year, things have been a bit quieter here as well. However, I have followed up with our development department once more. As soon as I have any updates, I will reach out to you - please bear with us a little longer. Thank you.
Thank you for your patience. We have just released an updated Latest Prerelease Service Pack, which should now address this issue as well:
…except during Preview operation in WebReportDesigner. Following API is called with bearer token in the URL and not as header. Can you please have a look.
I apologize for the inconvenience. I have created a support case for you where we can exchange further details on the new issue. We will then document the final result here in this thread.