I have an influxdb2 database running in kubernetes.
I can login to the web interface as admin
I can also access the pod running influx2 and run the influx command.
I cannot for the life of me figure out how to change the admin password.
There appears to be no way to do it via the web interface.
I haven't been able to find a way to authenticate on the CLI
Can someone assist?
From the CLI I get:
influx user password -n admin
Error: failed to find user "admin": 401 Unauthorized: unauthorized access```
Related
I'm trying to push an image to my gitlab registry which i previously built with success.
docker login registry.gitlab.com
I give the credentials and it returns me a "Login Succeeded"
Then, as always, i do a
docker push registry.gitlab.com/username/registry/base:latest
And it ends with
unauthorized: authentication required
i already tried to
docker logout registry.gitlab.com
and login again.
The process can be found here, it's pretty simple
link to github/gitlabhq
I'm used to do it like that, first time i face the issue, don't understand
Any help appreciated !
Ensure that your account has read/write access to the registry you are trying to access. What you might need to do is to create a new Access Token as there is a difference between API/Access tokens and your "normal" user password. Use this access token as described in the documentation (https://github.com/gitlabhq/gitlabhq/blob/master/doc/user/packages/container_registry/index.md#authenticate-with-the-container-registry)
docker login registry.example.com -u <username> -p <token>
The token can be created by going to Edit Profile -> Access Tokens -> Select Scopes -> Ticking off 'Read registry' & 'Write registry'
The Gitlab support told me this is due to a native limitation of the token duration.
You cannot customize this duration in Saas mode.
So pushing large image results in auto logout.
I'm currently using keycloak 15.0.1 keycloak container and i'm trying to configure the TOTP authentication (google authenticator) for the admin account in the default master realm. For this question purpose, i'll be using a local container.
The config is applied correctly when logging in from the web UI, but the problem is when using the admin-cli
I'm using the following command to log in the admin-cli:
sh ./kcadm.sh config credentials --server http://localhost:8080/auth --realm master --user admin --client admin-cli --password <my_password>
This works fine without the OTP setup, but when OTP is turned on, i'm getting the following error:
17:23:26,837 WARN [org.keycloak.events] (default task-9) type=LOGIN_ERROR, realmId=master, clientId=admin-cli, userId=94468ce6-a5b2-4b90-a993-476583f5e05e, ipAddress=127.0.0.1, error=invalid_user_credentials, auth_method=openid-connect, grant_type=password, client_auth_method=client-secret, username=admin, authSessionParentId=88f1c289-f9b7-4267-833a-084ccac99816, authSessionTabId=7HBaV7p3DhA
I've tried adding some params in case it would accept it:
--totp=
--otp=
-totp=
-otp=
It did not work, i've searched in keycloak documentation but i couldn't find anywhere on how to do it.
Has anybody tried and successfully connected to the admin-cli when using TOTP?
I can't login to WSO2 API Manager after installation.
I perform the installation as indicated in these steps: https://wso2.com/api-management/install/docker-compose/get-started/
API Manager for Docker Compose.
According to the instructions:
Running the product: Once WSO2 API Manager is successfully deployed,
access the following URLs on your favorite web browser using the
credentials username: admin and password: admin.
Try to login in https://localhost:9443/carbon/admin/login.jsp
I try, using user: admin password: admin, but I have this error message in the log:
api-manager_1 | [2021-02-20 03:19:36,643] ERROR - AuthenticationAdmin System error while Authenticating/Authorizing User : java.sql.SQLNonTransientConnectionException: Could not create connection to database server. Attempted reconnect 3 times. Giving up.
What am I doing wrong? thanks in advance.
Trying to login from docker to gitlab using the command:
sudo docker login registry.gitlab.com?private_token=XXX
But I still have the following error message:
Error response from daemon: Get https://registry.gitlab.com/v2/: unauthorized: HTTP Basic: Access denied\nYou must use a personal access token with 'api' scope for Git over HTTP.\nYou can generate one at https://gitlab.com/-/profile/personal_access_tokens
The token has the right access I doubled checked... I am rather new to docker, any hint/help? thanks!
The correct command line (that works in my case at least) was:
docker login registry.example.com -u <your_username> -p <your_personal_access_token>
If you are using 2 factor authentication, then personal access tokens are required.
More information on the following webpage,
https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
According to https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html, your username actually gets ignored:
Though required, GitLab usernames are ignored when authenticating with a personal access token. There is an issue for tracking to make GitLab use the username.
So, if you're not able to connect, it might not be because of the username.
When trying to deploy my container (or the hello world container) to google cloud run I receive this error:
ERROR: (gcloud.run.deploy) Cloud Run error: Internal system error. Missing necessary permission for service-<ID>#serverless-robot-prod.iam.gserviceaccount.com on resource <PROJECT ID>
I can see that the service account mentioned in the error is in my IAM dashboard and has the Google Cloud Run Service Agent role. I even tried giving it the Owner role, but it didn't work.
I tried including the --service-account flag with the same service account and receive this error:
PERMISSION_DENIED: Permission 'iam.serviceaccounts.actAs' denied on service account service-<ID>#serverless-robot-prod.iam.gserviceaccount.com (or it may not exist).
Which I know doesn't make sense.
I also tried this deploy through the console ui, but received the same error (the first one).
How do I fix this permission error?
I order to assign the iam.serviceAccounts.actAs permission you have to set the roles/iam.serviceAccountUser role.
You can do this by going to the Console > IAM & Admin and setting the Service Account User role to your service account.
Also, confirm that the Cloud Run runtime service account also has the iam.serviceAccounts.actAs permission. This is a requirement specified in the Cloud Run deployment permissions docs
As Dustin mentioned, there was an outage affecting IAM permissions. Now that the outage has been resolved, my deployment is working!