We are facing an issue on our application which uses google big query with OAuth authentication. When we run the application on docker container during runtime we get an authentication URL on the docker console like below :
Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=auto&client_id=330834658013-dg6niu0iihdcatin3c3mi6haqebrjinm.apps.googleusercontent.com&redirect_uri=http://localhost:61984/Callback&response_type=code&scope=https://www.googleapis.com/auth/bigquery%20https://www.googleapis.com/auth/cloud-platform%20https://www.googleapis.com/auth/drive
If we open the URL outside the container in the browser. We do not get the response and application get failed.
We tried to run the application other than docker container, we found that It automatically redirect to the browser and successfully get the response after that an folder named as 'credentials' containing StoredCredentials file is created locally which get referred next time for authentication.
As described above, due to authentication is not done by URL on docker container. The credential folder is also not created. Could you explain the resolution on priority.
We tried to run the application other than docker, It is running successfully. As it automatically redirect the URL and completes the authentication. Same is expected on docker container as well.
Related
I have a GCP project with a pipeline that scrapes a website at regular intervals. It has a cloud scheduler set up that posts to a Run container using an HTTP request (the container does the scraping). However, when I start the scheduler, the Run container logs just show a warning that says "[some_timestamp] POST 404 695 B [execution_time] Google-Cloud-Scheduler [Cloud_Run_URL]". I was confused because the scheduler posted the request to the right Run container, but the container is throwing a 404 error? What might be happening here?
If more information is needed, I will post it. Thanks.
Not the container is throwing 404.
A service, your web server on the container throws the 404.
So the request hits the container, then the webserver, but the requested URL doesn't work, and the web server returns 404. Look for your application errors, or if the path exists on the given URL.
Currently there is no outage occurring with any GCP services, which you can check in this status page. I suggest you try to emulate your Cloud Run container locally following this guide and using the Cloud Run emulation tool to test if the issue originates from your application instead of Cloud Run.
According to this thread comment, the 404 error might be returning from your web server and it is logged in Cloud Run. In this documentation page there are Cloud Run error codes and their meanings in addition to more troubleshooting procedures.
I'm trying to deploy a parse application according to this document https://aws.amazon.com/it/blogs/mobile/how-to-set-up-parse-server-on-aws-using-aws-elastic-beanstalk/ .
I deployed the application in aws, created a mongolab cluster, copied the connection string in the environment panel and started the application.
If I try to test using curl according the aws tutorial I receive an interval server error.
How can I understand what's the problem?
I'm running Ws02 products in docker containers
I have a strange problem. I publish an API in publisher, subscribe to it using the store and access the API using the curl command. It works fine. The DB is also running in a separate mysql container and Im persisting the DB data to a volume. However, if I shutdown the containers (docker-compose down) , bring it back up and access the API again, I get a 404 error with the following errordetails .Any idea?
errorCode":900000
errorDescription":"Not Found""
errorDetails":"The requested resource is not available
404
In API Manager, some API data is persisted in the File system as well. You can see the artifacts located at "/repository/deployment/server/synapse-configs/default/api. You need to make sure this is not replaced when the docker container is restarted.
I am executing sample programm of wso2. I have installed wso2is on different machine and tomcat is on local machine. I have changed localhost:9443 to my ipaddress(eg 192.168.1.xxx) from travelocity.properties and avi.properties. But when I execute sample from click on login button it always redirecting me localhost and giving error.
I think you need to try the following,
While the tomcat is running,
Open the travelocity.war with an archive manager
Edit the travelocity.properties file,
update SAML2.IdPURL value
eg : SAML2.IdPURL=https://192.168.1.7:9443/samlsso
Save and update the travelocity.com web app
Restart the tomcat server just to be sure (You don't really have to do this since tomcat hot deploys once it detects a change)
I tried this locally and it redirected me to the IP address I put in SAML2.IdpURL. Clearly the problem seems to be a configuration error on the travelocity.com web app side :)
You need to change <HostName> and <MgtHostName> attributes at repository/conf/carbon.xml of your Identity Server with your IP address. By default they are set as localhost, so when logging it will be redirected to location specified there.
I am testing the JNDI datasource with sample downloaded from url [1]. I upload the app as a tenant, and register the datasource in the context.xml of the app.
upload the app to AS, with no version number, click go to URl and find the app is working, and achieve the data from database; delete the app from the console, upload the app to AS, with version number 0.1.2
then the back-end console show some errors:
[2013-12-17 17:18:13,816] ERROR {org.wso2.carbon.tomcat.internal.CarbonTomcat} - Webapp StandardContext[/carbonDSwebApp/0.1.2] failed to deploy
[2013-12-17 17:18:13,817] ERROR {org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer} - Error while deploying webapp: StandardContext[carbonDSwebApp#0.1.2.war].File[F:\OPENSO~1\WSO2\WSO2AS~1.0\bin..\repository\deployment\server\webapps\carbonDSwebApp#0.1.2.war]
org.wso2.carbon.tomcat.CarbonTomcatException: Webapp failed to deploy
Caused by: java.lang.NullPointerException: no !/ in spec
then no matter how many times of deletion and upload, this app is no longer able to be ploaded.
[1] http://dinushasblog.blogspot.com/2011/12/how-to-access-carbon-data-source-from.html