I'm using Zeppelin 0.7.3 version . On trying to use the zeppelin REST API call(http://localhost:8080/api/notebook/2D8BSC25C/paragraph/20180211-213728_2111839943)in postman to update paragraph , am getting the Method not allowed error eventhough the given input were correct.
Thanks in advance.
In version 0.7.3 you can only update paragraph configuration -> docs.
The full paragraph update will be available in the future releases.
Related
Loopback 4 is showing a version number in the Api explorer and I'd like this version to follow the version of my component that is specified in the package.json .
How can this be achieved ?
Regards,
At this moment, you can modify the spec manually. First get the application's OpenAPI spec by calling app.restServer.getApiSpec()
Then modify the spec accordingly (change the version inside info to be the same as the version in package.json), and setting the new spec by calling app.api(your_new_spec)
LoopBack team is building an OpenAPI spec enhancer service to make ^ automatically happen by applying spec enhancers. See the usage and demo documentation in Extending-OpenAPI-specification
After finishing story Adding an enhancer service in the rest server, you will be able to modify the spec by applying your enhancer.
I am trying to use a payment module in OpenCart version 2.0.1.1, and I need to update our Hash to HMAC-SHA-512, so the checkout page authorizes successfully.
I just don´t know how to change the hash and where exactly I can do this.
We use Plesk, with PHP 7. The domain is www.didikong.de
The payment module is WireCard Checkout Page version 1.2.0.
So this wirecard generates a Fingerprint, which is encrypted via HMAC-SHA-512. And our website uses SSL.
Thanks in Advance.
I am really not sure if the version 1.5.2 of opencart-wcp was still compatible with 2.0.1.1 but I would try that first. There was a client library update between 1.2.0 and 1.5.2 in which the algorythm was updated. If you don't have a test system where you could try it out just check the changes in the client lib. More in particular look into the /system/library/wirecard/vendor/wirecard/checkout-client-library/library/WirecardCEE/QPay/FrontendClient.php file and see if the setHashAlgorithm is using the WirecardCEE_Stdlib_Fingerprint::HASH_ALGORITHM_HMAC_SHA512 constant. If not, just change it to the mentioned constant and you should be good to go. If you get any errors regarding some missing things consider updating the /system/library/wirecard/vendor/wirecard/checkout-client-library/library/WirecardCEE/Stdlib/Client/ClientAbstract.php to the newest version.
We are trying to implement CORS support in our APIs, and it we are getting an error from API Manager that is exactly the same as what is described here.
We are using API Manager 1.3.
Can someone confirm that there is no way to support OPTIONS with API Manager 1.3? We don't want to upgrade to 1.4 at this time.
There was another issue which we found when using PUT and OPTIONS method from APIs as described in [1].
This was fixed with AM 1.4.0.Hence better option is to upgrade to 1.4.0 as it contains fix for both your mentioned issue and mine mentioned one.And additionally AM 1.4.0 contains several new features with it.
[1] https://issues.apache.org/jira/browse/SYNAPSE-919
Thanks;
A lot of good forums explain how to create the PIP in WSO2IS v 3.2.3 http://xacmlinfo.com/2011/12/18/writing-jdbc-pip-module/ and http://blog.facilelogin.com/2011/04/xacml-policy-information-point.html
I tried the first link and everything works for me.
However version WSO2 4.1.0 which supports XACML 3.0 (for which I use it) does not allow the same way of PIP creation , it does not have entitlement-config.xml, how to create PIP in WSo2IS version 4.1.0 , maybe anyone knows ?
Thank you !
There are some config file and API changes with Identity server 4.x.x version. It seems to be that blog post has been updated by mentioning it [1]. Please check it again. However you can find the sample from here [2]
[1] http://xacmlinfo.com/2011/12/18/writing-jdbc-pip-module/
[2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/components/identity/org.wso2.carbon.identity.samples.entitlement.pip/
You would have to use CARBON_HOME/repository/conf/security/entitlement.properties to add your attribute finder and the properties required.
The blog post [1] would be helpful if you are using 4.x.x
[1] http://blog.ashansa.org/2013/09/write-simple-jdbc-pip-attribute-finder.html
I'm working through a tutorial that uses Apache CXF 2.6.2 to create a RESTful web service. I installed version 2.7.1 (the latest at the time), because the tutorial indicated that any version 2.6.2 or later would work, and I figured why not use the latest. I am creating the client, and the tutorial directs me to use org.apache.cxf.jaxrs.client.ResponseReader. The problem is that Eclipse tells me "ResponseReader cannot be resolved to a type" and trying to import the class also gives an error. I searched the internet some, and it sounds like ResponseReader is no longer available in CXF 2.7.x. My question is, what is the alternative to ResponseReader in 2.7.x to represent the return value of a REST invocation as XML?
Quoting this web page:
JAX-RS: 3 classes have been removed from the org.apache.cxf.jaxrs.client package: ResponseReader... The first class in the list is not needed with JAX-RS 2.0 Response class...
So, I guess that answers my question. There is no replacement per se, it's just not needed anymore.