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.
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'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.
In application.properties i've specified :
vaadin.servlet.productionMode=true
and relaunched application server. However, I still can relaunch app via adding ?restartApplication at the end of url. According to documentation, productionMode=true is cure for this.
The question is - did i miss something?
Thanks
You didn't miss anything, ?restartApplication works also in production mode.
I can't access most of the Sonar API, for example
localhost:9000/api/tests/show?key=htmlparser:/src/test/java/HtmlParserTest.java
or see api/sources/scm. api/server/system and some other general stuff works but nothing where I actually see the code.
I always get a
{"errors":[{"msg":"Insufficient privileges"}]}
I set the project permissions to let anyone see source code & browse the porject, I tried it with Postman, a Java HttpRequest, the command line ...
curl -u admin:admin localhost:9000/api/tests/show?key=htmlparser:/src/test/java/HtmlParserTest.java
I checked with SonarQube 5.1 and 4.5.1. I've found a posts with the same issue but have yet to find a fix. Does anyone have a solution idea?
Thanks for your help
SOLUTION
It was a syntax error (even though the message said Insufficient privileges). The correct call would be:
localhost:9000/api/tests/show?key=htmlparser:htmlparser:src/test/java/HtmlParserTest.java
If you are not sure what goes before the "src/..." don't worry. You can get it by calling api/projects/index and looking at the attribute named "k".
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