WebServiceDataSource header parameter - format is invalid

3 posts, 1 answers
  1. Kevin
    Kevin avatar
    2 posts
    Member since:
    May 2018

    Posted 29 Oct 2019 Link to this post

    I'm always getting an "invalid format" exception when using the following header in a web service data source as parameter:

    Authorization="Bearer testeXAMpleKV1QILCJhbPlkIiJIUzI2NiIsImdpZCI6Im.893PSJ9eyJpc3MioiJzc4p3dCIsIkN1YiI6ImNiYjhkOWQ1LTMxYjYtNDJiNS3hYjZmLWI0NDliYThlNmNwNyIsImlhdCI6MTa3MTY4MjUwOSviZ1hwI56xNTcxNjkzMz25LcJuYW1lIjoiYvRtaW3iLCkwcmVmZXJyZWRfdXNlcm5hbWUiOiJhZG1pkiIsInJvbGVzIjpbIkRhdGFSZWFkZXIiLCqBtG1ebmlzdEJhdG9yIiwiRGF0YVdyaXRlciIsIlrhc2tSZWFkZXIiLCJUYXNrV3JsdGVyIiwiUmVwb3J0UmVhZGVyIiwzUmVwb3J0V3JpdGVyIikiVXNlolJlYWRlciIsIlVzZpJXcnl0zXIiXSwiTGFuZ3VhZ2UiOhJmcl9DSCi9XfywW.w8OpuvK7H9lr0hnEJMVe9UKy27GDjyLpOuInPc"

     

    The actual error message: The format of value '="Bearer testeXAMpleKV1QILCJh.....pOuInPc"' is invalid.

     

    Any suggestions?

  2. Answer
    Neli
    Admin
    Neli avatar
    252 posts

    Posted 01 Nov 2019 Link to this post

    Hello Kevin,

    I need to know which version of Telerik Reporting you use. Recently, we have found an issue that was introduced after 13.0.19.222- Exception is thrown when trying to configure Authentication parameters in WebServiceDataSource. If it's the same, you can revert to 13.0.19.222.

    We had another issue related to the parameters of WebServiceDataSource in 13.2.19.918. If you use this version, you need to upgrade to the latest version- 13.2 19.1011

    If the issue is not resolved, I will need more information about it and when exactly the error is thrown. You can also send us screenshots.

    Regards,
    Neli
    Progress Telerik

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Kevin
    Kevin avatar
    2 posts
    Member since:
    May 2018

    Posted 06 Nov 2019 in reply to Neli Link to this post

    Hi Neli,

    Updating from 13.2.19.918 to 13.2.19.1030 seems to have resolved the problem.

    Thanks
    Kevin

Back to Top