I'm trying to access a https site from Apache Nifi that has informations that I'm intrested at. The problem is it needs authentification to access the site.
With InvokeHTTP in Apache Nifi, we only can have the 'Basic Authentification' that I don't even know what stands for, but when inserting my logging identification, nothing changes. and I have a Access denied to that site (
<?xml version="1.0" encoding="UTF-8"?>
<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<m:code>-2147024891, System.UnauthorizedAccessException</m:code>
<m:message xml:lang="en-US">Access denied. You do not have permission to perform this action or access this resource.</m:message>
</m:error>
).
I've been looking for answers about a week ago, and I can't seem to find the answer anywhere,
That's why I'm asking you guys for help.
Thank you in advance.
I am a newbie to wso2. I just manage to bring up the emm site. But when I try to add my device to the device manager, I find that the QR code generated always has URL with domain localhost. When I look into the logs, it has something like this:
./repository/logs/wso2carbon.log:TID: [-1234] [] [2016-08-22 15:54:05,887] INFO {org.jaggeryjs.jaggery.app.mgt.TomcatJaggeryWebappsDeployer} - Deployed webapp: StandardEngine[Catalina].StandardHost[localhost].StandardContext[/store].File[/opt/wso2emm-2.0.1/repository/deployment/server/jaggeryapps/store]
So, I think I need to config the variable StandardHost to domain I needed. But I can't find a place for that. Any idea? Thanks.
You can find the relevent config in the Following file.
<EMM_HOME>/repository/deployment/server/jaggeryapps/emm/config/config.json
Also you refer the documentation here.
I am trying to create a Google sign-in and getting the error:
Permission denied to generate login hint for target domain
Before you mark this a duplicate, this is not the same as the question asked at Google sign in website Error : Permission denied to generate login hint for target domain because in that case the questioner was on localhost, whereas I am getting this error on the server.
Specifically, I have included the url of the server in the Authorized Javascript Origins, as in the following image:
and when I get the error, the request shows that the same url was sent, as in the following image:
Is there something else I should be putting in my Restrictions page? Is there any way to figure out what is going on here? Is there a log at the developer console that can tell me what is happening?
Okay, I figured this out. I was using an IP address (as in "http://175.132.64.120") for the redirect uri, as this was a test site on the live server, and Google only accepts actual urls (as in "http://mycompany.com" or "http://localhost") as redirect uris.
Which, you know, THEY COULD HAVE SAID SOMEWHERE IN THE DOCUMENTATION, but whatever.
I know this is an old question, but it's the first result when you look for the problem via Google, so I'll share my solution with you guys.
When deploying Google OAuth service in a private network, namely some IP that can't be accessed via the Internet, you should use a magic DNS service, like xip.io that will give you an URL that your browser will resolve to your internal IP. You see, Google needs to be able to reach your authorized origin via your browser, that's why setting localhost works if you're serving it on your computer, but it won't work when you're deploying outside the Internet, as in a VPN, intranet, or with a tunnel.
So, the steps:
get your IP address, the one you're deploying at and it's not a public domain, let's say it's 10.0.0.1 as an example.
add http://10.0.0.1.xip.io to your Authorized Javascript Origins on the Google Developer Console.
open your site by visiting http://10.0.0.1.xip.io
clear your cache for the site, if necessary.
Log in with Google, and voilà.
I got to this solution using this answer in another question.
If you are using http://127.0.0.1/projects/testplateform, change it into http://localhost/projects/testplateform, it will work just fine.
If you testing in your machine (locally). then dont use the IP address (i.e. http://127.0.0.1:8888) in the Client ID configuration , but use the local host instead and it should work
Example: http://localhost:8888
To allow ip address to be used as valid javascript origin, first add an entry in your /etc/hosts file
10.0.0.1 mydevserver.com
and then add this domain mydeveserver.com in Authorized Javascript Origins. If you are using some nonstandard port, then specify it with your domain in Authorized Javascript Origins.
Note: Remove your cache and it will work.
Just ran across this same issue on an external test server, without a DNS entry yet. If you have permission on your local machine just edit your /etc/hosts file:
175.132.64.120 www.jimboweb.com
And use use http://www.jimboweb.com as an authorized domain.
I have a server in private net, ip 172.16.X.X
The problem was solved with app port ssh-forwarding to my localhost port.
Now I am able to use deployed app with google oauth browsing to localhost.
ssh -N -L8081:localhost:8080 ${user}#${host}
I also add localhost:8081 to "Authorized URI redirect" and "Authorized JavaScript sources" in console.developers.google.com:
google developers console
After battling with it for a few hours, I found out that my config in the Google Cloud console was all correct and similar to the answers provided. Due to caching issues or something, I had to recreate a OAuth Client ID and then it suddenly started working.
Its a pretty old issue, but I encountered it and there wasn't any helpful resource, as such I am posting my solution.
For me the issue was when I hosted my web-app locally, a using google-auth for logging in.
The URL I was trying to hit was :- http://127.0.0.1:8000/master
I just changed from IP to http://localhost:8000/master/
And it worked. I was able to log in to the website using Google Auth.
Hope this helps someone someday.
install xampp and run apache server,
put your files (index and co) in a folder in the xampp dir (c:\xampp\htdocs\yourfolder).
Type this in your browser url - http://localhost/yourfolder/index.html
I have problem with displaying my WSDL. I have found a way to dynamic read it from my XSD schema and now i am doing this as:
<sws:dynamic-wsdl id="test"
portTypeName="testPort"
locationUri="/"
targetNamespace="http://testnamespace">
<sws:xsd location="/WEB-INF/test.xsd"/>
</sws:dynamic-wsdl>
this way i got under address : localhost:localport/applicationname/id.wsdl WSDL which in my case is : localhost:8080/MyApp/test.wsdl.
Thing i want to achive is to display this WSDL after executing another request: localhost:8080/MyApp/test.aspx?WSDL How can i edit my code to do so? Can anyone redirect me somewhere if it is described ? I thought about creating a wsdl file instead of xsd but do anyone have an example how to show under specyfic address wsdl file?
From mine experience I recommend You modify your proxy_ajp configuration file add:
ProxyPass /MyApp/test.aspx?WSDL ajp://localhost:8080/MyApp/test.wsdl
then restart your httpd. After this operation all request coming for localhost:8080/MyApp/test.aspx?WSDL will giving the localhost:8080/MyApp/test.wsdl result
I have a greg instance with context root established (url access
https://host:9443/greg/carbon/admin/index.jsp
When I try to access the governance dashboard, all the gadgets show the same message.
Unable to retrieve spec for http://host:80/registry/resource/_system/config/repository/dashboards/gadgets/impact-analysis.xml. HTTP error 404
Note the gadget is trying to access to the root context without the /greg/ prefix I have stablished.
Any help to solve this will be very appreciated.
Thank you
Pablo
This issue is appearing when you set both HostName and WebContextRoot in carbon.xml.If you changed only the WebContextRoot this issue is not appearing.This is a known issue found in WSO2 GREG 4.1.1 and it is now fixed in trunk [1].
As a workaround can you keep the <HostName> entry as it is in carbon.xml and only change the web-context root and try.
[1] https://wso2.org/jira/browse/CARBON-11839
Thanks;
/Lalaji