How to run kibana after the complete setup? - kibana

Kibana has been setup with the password and token (which is generated when running elasticsearch in cmd) and setup is done.
After this how to open/run kibana again it is asking token again( since token expire every 30 mim)
If I run the elasticsearch again I am not getting new password and token(tried with the command to generate new password and token the commands are not working for me)
I am just asking how to run kibana once we close after using it? (How to open the application again? )

Related

Facebook API v3.2 connection issue with Rfacebook package in RStudio

I'm connecting to Facebook API v3.2 in order to get my friends information. I had the following error:
Invalid Scopes: user_relationships, publish_actions. This message is only shown
to developers. Users of your app will ignore these permissions if present. Please
read the documentation for valid permissions at:
https://developers.facebook.com/docs/facebook-login/permissions
How to fix this issue using API v3.2?
I have proceeded to the following steps:
I connect to the Facebook API via App: I have created a new Facebook APP (from https://developers.facebook.com) and set it up by default.
I connected to the Facebook API v3.2 via authentication token (from https://developers.facebook.com/tools/explorer) and I obtained access token of all necessary permissions.
I used this R code in RStudio to connect to my API:
install.packages("devtools")
library(devtools)
# I used install_github to get the updated version of Rfacebook package
install_github("pablobarbera/Rfacebook", subdir="Rfacebook")
require (Rfacebook)
I used this fb_oauth to connect my R session with the App I already created and authenticate it to my Facebook profile for Data Mining.
fb_oauth <- fbOAuth(app_id="My_APP_ID", app_secret="MY_APP_SECRET_KEY", extended_permissions = TRUE)
I expect that the token will give access to some of the authenticated user's private information (birthday, hometown, location, relationships) and that of his/her friends, and permissions to post status updates as well as to access check-ins, likes, and the user's newsfeed.
But I got the following error on RStudio command line.
Copy and paste into Site URL on Facebook App Settings: http://localhost:1410/
When done, press any key to continue...
Waiting for authentication in browser...
Press Esc/Ctrl + C to abort
Authentication complete.
Error in oauth2.0_access_token(endpoint, app, code = code, user_params = user_params, :
Bad Request (HTTP 400). Failed to get an access token.

Apache Airflow: User creation, access and permissions on DAG

I am using airflow (1.8.0) and using web UI I can create a user but it doesn't allow me to set a password. But is it possible via command line to
create new user with password
assign role/permissions to a user
how to limit and manage access of user/group so that they cannot change or trigger someone else's DAG
I have seen apache-airflow (1.10.0) which does have cli feature to create a user with password (https://airflow.apache.org/cli.html#create_user), but cannot see anything around setting access level and permissions.
Airflow 1.8.0 doesn't support CLI password creation.
You can create user and set a password as it is described here.
Airflow 1.10.0 doesn't allow to manage permissions for a given user, future releases should have this feature.

How to change the password for phpmyadmin

Recently I installed the Bitnami Wordpress canned deployment on Google Cloud Platform.
I can view the phpMyAdmin instance at a local address (http://127.0.0.1:8888/phpmyadmin/) but I cannot determine the username and password to log into the database cluster. I have tried the username specified in Deployment Manager, but the temporary password is not working. When I attempt to login, I receive the following error:
mysqli_real_connect(): (HY000/1045): Access denied for user 'user'#'localhost' (using password: YES)
I have tried to use various common passwords, such as root/root, with no success. If we assume the password is lost, how I can I figure out the password, recover it, or change it by using an SSH shell to the hosting compute instance?
Resetting password by supporting team if possible try
This issue seems related to phpmyadmin. I found this similar post where they stated:
This is asking for your MySQL username and password.
You should enter these details, which will default to "root" and ""
(i.e.: nothing) if you've not specified a password.
UPDATE
Have you tried to create a new user or change the password? Check this guide on how to do it.
Bitnami Engineer here,
As our guide mentions, once you create the SSH tunnel to access phpMyAdmin, you need to use the user 'root' and the password we configure at boot time (it's the same password we configure in the application). More information in our documentation
https://docs.bitnami.com/google/components/phpmyadmin/
Oh it's opened now, the user was (root) which it's not mentioned anywhere when i created the instance, the password is the one which generated by Bitnami when the instance is created on the bitnami platform lunchpad website.
the password is used for 2 users :
username: user
username : root (hidden) for new users who are decided to try cloud servers is not easy to figure this username and which password must use.
thanks for trying to help.

can't configure data for CORS due to other email being associated with project

I am trying to configure my google storage for Firebase to allow cross origin uploading using gsutil and a cors.jsonfile. I enter the following command in my project where the cors file is located:
gsutil cors set cors.json gs://nameofproject.appspot.com
I get the following error message:
AccessDeniedException: 403 someOtherFirebaseAccount#gmail.com does not have storage.buckets.get access to bucket apptotest.appspot.com
I am not currently logged in with someOtherFirebaseAccount -- I verify this by running firebase login and seeing that my current, desired account is the active one.
firebase login
Already logged in as desiredAccount#gmail.com
Any ideas what could be going wrong here?
If you're using the version of gsutil that comes packaged with gcloud, it will use credentials for your currently logged in gcloud user (this is usually the last user you activated via gcloud auth login). You can check which user is active by running gcloud auth list.
If you're not using the gcloud-packaged version of gsutil, you can run gsutil config and log in as the desired user.

Here API - These credentials do not authorize access - Some Requests

Im getting some 403 errors in some HERE position requests. Looks like that the servers are not synchronized.
My Account was created 2 weeks ago.
{"error":{"code":403,"description":"These credentials do not authorize access. Please contact your customer representative or submit a request here https://developer.here.com/contact-us to upgrade your account. You can also get valid credentials by registering for a free trial license on https://developer.here.com.","message":"Forbidden"}}
First, generate apiKey and bearer token in your here account. For the apiKey go to your profile, create a new app and then you can generate it under Credentials -> API Keys.
For the bearer token, you first need to create oauth tokens (under Credentials -> OAuth), download the credentials.properties file, then use their CLI to generate the bearer token. Before you can use the CLI, you need to install it and then set it up.
I'm on a mac, so for me this installed it:
$ brew install heremaps/olp-cli/olp
Follow instructions on their page for whatever OS you have. Now you are ready to generate the bearer token. Make sure you are in the same directory where you downloaded the credentials.properties file earlier:
$ olp credentials import default credentials.properties
Generate the token:
$ olp api token get
Now you have everything to do a call to their API (replace HERE_API_URL with the one you want. They have many different ones for various use-cases):
GET
https://{HERE_API_URL}?apiKey={YOUR_API_KEY} -H 'Authorization: Bearer {YOUR_TOKEN}'
Note: Do not use app_code and app_id. These have been deprecated.
I had the same issue when I had only one API key created. Once I created a second API key, the issue went away.
Make sure you have two API keys generated, even if you only use one. The documentation suggests setting two keys but it never mentions it's required.

Resources