I'm trying to add a netconf-connector into my Open Daylight Nitrogen controller and keep coming up against this error:
">Error parsing input: Could not find module for namespace urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"
I'm posting to rest via the postman application using the below URL and Schema used in the guide below:
"http://192.168.0.1:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules"
Has anyone had the same issue, this is the guide I'm following..
http://docs.opendaylight.org/en/stable-nitrogen/user-guide/netconf-user-guide.html
I found the same issue reported on the old Open Daylight forum but it went un-answered..
https://ask.opendaylight.org/question/28561/error-adding-node-to-odl-via-restconf/
Thanks,
Simon
Judging from the error message, you tried to use the controller-config loopback mechanism. This mechanism was deprecated and I believe was completely removed in Nitrogen (unfortunately the documentation wasn't updated to indicate this). Either way, you should use the mechanism outlined in the "Netconf-connector configuration with MD-SAL" section.
Related
One quick question. As of last week I had completely setup the AEM SDK with the Venia store front with all the components working. When I move the setup the AEM publish SDK, I am encountering one issue.
The /api/graphql is throwing 403 errors which means no frontend commerce operation is happening on the storefront.
I tried adding the /api/graphql to the CSRF filter's exclude list and even removed the POST method from there.
After this I still 403 on GET request of /api/graphql and the following on POST request.
I am I missing some setting?
Note: on the sling servlet resolver config, I have added the /api/graphql but there is no change.
There is a query very similar to this on the groups but there is no response. So thought of raising it here.
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-cif-magento-on-publish...
Please let me know if I am missing something.
Issue solved.
I introduced a var called COMMERCE in the global vars to solve the problem, since the vhost file refers to it.
I could have done it slightly better but I guess i was lazy :)
Please refer to this link for details:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-cif-magento-on-publish/m-p/442185#M31799
I am using UAA "cloudfoundry-identity-uaa-4.14.0.war" and could see there are no where i can change the log level. Few places i have changed but that does not work. Even tried using the latest version which is 4.30.0, but still it doesn't work. Can anyone please suggest some solutions?
uaa.logging_level appears to be in reference to a property supported by the BOSH release. There is no direct equivalent in the UAA.
I am currently testing the changes for version 4.0 of the protocol for PSD2 using Direct Integration.
I am running under Visual Studio using a localhost website address.
When calling the SagePay payment endpoint with ThreeDSNotificationURL set as a localhost address (http://localhost:15536/Payments/ThreeDResponse) I receive the following error '3228 : The ThreeDSNotificationURL field format is invalid.'
If I change this field to a fully qualified domain (http://www.google.com) I no longer receive the error, but can't complete my testing.
Using localhost for the termurl in version 3.0 of the protocol works as expected.
I was attempting to work locally like your self and receiving the same issue. After speaking with support they confirmed that they will not accept "localhost". Also, the documentation suggests that HTTPS is a requirement, so this might also be a blocking factor.
I think someone suggested using ngrok as a means of tunneling external requests into your localhost, which is a good method to continue development locally whilst also being visible externally to services like SagePay.
Once I got passed the above issue, I got several more errors for other missing required fields as listed here; https://www.sagepay.co.uk/support/38/psd2-under-direct-integration (note that if BrowserJavascriptEnabled is true all conditional fields are then required)
Did you URL encode the ThreeDSNotificationURL in your post?
I send it like that and it is ok:
sb.Append(HttpUtility.UrlEncode("https://www.clientdomian.com/ac/ThreeDSNotificationURL.aspx"));
I run the site on my local IIS for development.
I recently had this issue and I wanted to document it here, because searching for this issue gives very little in terms of results.
I was getting this error code when i switched my Opayo/SagePay extension (MageNest SagePay for Magento) to 3ds2.
As it turns out, the full URL wasn't being sent. It was trying to send sagepay/direct/postBack?form_key=HZuYxgiEq9w2CNFB and NOT https://www.example.com/sagepay/direct/postBack?form_key=HZuYxgiEq9w2CNFB. It's partly my fault because there was a domain field in the config which was empty (it's not like the domain can't be retrieved automatically, huh) and partly the vendors fault because it was very badly documented.
So while this is a different problem for a different platform, I hope this helps someone.
I have searched the answers to similar questions asked about this SagePay error, and checked that the fixes don't appear to apply to my problem.
Specifically:
I am using a correct 2-letter country code for BillingCountry and DeliveryCountry.
I am POSTing VPSProtocol, TxType and Vendor as well as the Crypt value.
I have re-checked that I am using the correct encryption key from the MySagePay test portal.
Now I was using http://localhost:8084/app/success and http://localhost:8084/app/failure for my success and failure URLs, since I thought that although these are (obviously) not visible externally, it shouldn't matter since SagePay is re-directing at the end of its part of the transaction. (Is this assumption correct, or do these URLs need to be externally accessible?) Some of the answers have thrown doubt on this, so I changed them to an external website I own, and I still get the same error.
Another line of thought is that the client I am developing for has already gone live, and there seem to be hints that once you have gone live, you no longer have access to the test server (Is this true?)
Is there anything else I should be checking? (Additional info: I'm using the SagePay api (sagepay-api-1.2.2.0.jar and related libraries) to validate the form contents and encrypt them.
I used the integration from https://github.com/tolzhabayev/sagepayForm-php
I had this error (5080) and spoke to SagePay support and they guided me to the MySagePay portal where you can view Invalid transactions to be able to troubleshoot this error easily!
Hope this helps someone.
Chris Rickards
I had exact same problem and I tried everything that you described as well, one day after I found that the problem was in "VendorEMail" field, it had 2 email addresses separated by ;, once I removed second and left only one email everything worked.
I just implemented a simple login functionality using spring it how ever worked with the eclipse in built browser but gives the following error in chrome and firefox.
HTTP Status 404 - /SpringLogin/welcome.jsp;jsessionid=8332D4F3D4709DCA37C87F30F1EA03D5
The requested resource (/SpringLogin/welcome.jsp;jsessionid=BEE789093FF79CB6B67F8DA368E8B3E4) is not available.
can you please tell me why it is happening?
PS: I have two projects SpringLogin and both of them had same project names and both had similar packages. Then neither of the projects worked properly and gave the above error. How ever after I created another project with a different name and using different package names, it worked like magic. I am guessing here that it may have been the problem. But what is the logical answer that'll explain what happened there?
you don't have being calling the correct URL
it seems that the context /SpringLogin/ does not exists anymore.
Try /welcome.jsp or if you changed the name of application - try /newappname/welcome.jsp