Oracle Analytics Publisher

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Can we send REST messages to BIP/OAS without %2F separating folders?

Accepted answer
11
Views
2
Comments
Rank 1 - Community Starter

Hi,

We would like to send REST messages to OAS that do not contain the %2F characters in place of "/" characters for the report path.

This Works - after the v1/reports/ endpoint we must use %2F in place of / characters to define the Shared Folders subfolder path
https://xxx.ocs.oc-test.com/customer-test/bip/xmlpserver/services/rest/v1/reports/MyFolder%2FMy+Report.xdo/run

This Does Not Work - we would like to NOT use the %2F values so that we can configure our AWS API tool security
https://xxx.ocs.oc-test.com/customer-test/bip/xmlpserver/services/rest/v1/reports/MyFolder/My+Report.xdo/run

Our use case is we will have a few boundary systems that need to run BIP reports as APIs. We want to control what reports each service account has access to. Our boundary systems do not access the BIP endpoints directly, rather security is controlled within an API Gateway. For example, user 1 will have access to reports in the "MyFolder", and user 2 will have access to reports in the "OtherFolder". Our API Gateway does not allow us to configure variables/rules containing the %2F characters. We can workaround our issue by leveraging custom code instead of configuration but prefer to avoid that and reconfigure BIP if possible.

Thanks,
Jeramie

Tagged:

Best Answer

  • Rank 1 - Community Starter
    Answer ✓

    Hi Gianni,

    Thank you for your response. I agree that Oracle is unlikely to change anything. I was more wondering if there was a server setting to change this behavior. I'm working on our SaaS and BIP side, not our Integration and API Gateway side. I'll forward your recommendation and reasoning to them.

    Thanks again,
    Jeramie

Answers

  • Hi,

    Our API Gateway does not allow us to configure variables/rules containing the %2F characters.

    I see what you are saying, but did you try asking your API Gateway provider to just support %2F (which is a perfectly valid component of a URL) instead of asking Oracle to rewrite the Publisher API?

    Because it isn't a parameter, that's how the API works: in so many places (most places actually) paths in Oracle Analytics products are part of URLs as parameters, and because they aren't a URL but a parameter, they do use the encoded version of / to make that difference.

    I really doubt that something can be done, or that something will be done for that.

    Obviously, this is my opinion, maybe somebody else has a solution for that, or if none is provided you can always post an idea to have that parameter/configuration/change evaluated for future implementation.

Welcome!

It looks like you're new here. Sign in or register to get started.