I have set anonymous access enabled for the read operations in the docker. But when I try to pull an image from the repository it asks for an authentication password.
What is the correct way to set anonymous read access to the docker repository ? I have followed this documentation
https://www.jfrog.com/confluence/display/RTF/Managing+Permissions
Following is the error
Error response from daemon: Get https://my-repo/v2/nginx/manifests/latest: unknown: Unauthorized
Related
I am currently trying to build my first pipeline. The goal is to download the git repo to a server. In doing so, I ran into the problem that I have 2FA enabled on my account. When I run the pipeline I get the following error message:
remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password.
Pipeline:
download_repo:
script:
echo "Hallo"
As far as I understand I have to use a PAT because I have 2FA enabled. But unfortunately I have not found any info on how to use the PAT.
To access one of your GitLab repository from your pipeline, you should create a deploy token (as described in token overview).
As noted here:
You get Deploy token username and password when you create deploy token on the repository you want to clone.
You can also use Job token. Job token inherits permissions of the user triggering the pipeline.
If your users have access to the repository you need to clone you can use git clone https://gitlab-ci-token:${CI_JOB_TOKEN}#gitlab.example.com/<namespace>/<project>.
More details on Job token is here.
The OP Assassinee adds in the comments:
The problem was that the agent could not access the repository.
I added the following item in the agent configuration:
clone_url = "https://<USER>:<PAT>#gitlab.example.com"
This makes it possible for the agent to access the repository.
{"successStatus":2,"error":"The user name or password is incorrect [userName=[testuser]]","sessionToken":null,"response":null}
Getting this REST API response on triggering authorization call for Ignite with following command:
curl "http://localhost:8080/ignite?cmd=version&ignite.login=[testuser]&ignite.password=[password]"
I have already created this user via sqlline interface of ignite with
create user "testuser" with PASSWORD 'password';
this command.
Authentication is enabled in my cluster configuration file. Please tell me how I can get rid of this error, where I have mistaken or missed any step.
Thank you in advance.
In my work I give support to users, and the following problem has been sent to me.
Logs Jenkins: (Automated tests that run in the night)
[HttpAuthenticationRequestFilter$UPDCredentialsProvider] Domain
request authentication with the realm 'dolmen'
Logs Server:
23/01/2018 01:28:25.637 [http-thread-pool-8080(15)] WARN java.util.logging.Logger.doLog WEB9102: Web Login Failed:
com.sun.enterprise.security.auth.login.common.LoginException: Login failed: Security Exception
23/01/2018 01:28:25.646 [http-thread-pool-8080(29)] ERROR java.util.logging.Logger.doLog jdbcrealm.invaliduserreason
Via asadmin I've checked that the realm dolmen exists
asadmin> list-auth-realms
Authentication failed with password from login store: /root/.asadminpass
Enter admin password for user "admin">
admin-realm
file
certificate
dolmen
pnf-realm
Command list-auth-realms executed successfully.
asadmin>
What could be the problem?
UPDATE 1)
I was able to reproduce the error in SOAPUI. During the call to the web service, I noticed that if I change a letter in the login user or password, I can see the error message : " request authentication with the realm 'dolmen'"
Log SOAPUI:
But as you can see, in the image "Log SOAPUI:" I also have a HTTP 401.
In SoapUI Preferences, I notice that the option "Authenticate Preemptively" was disable. After enable the option "Authenticate Preemptively" I was able to finish a test in my local machine without error.
In the machine where Jenkins is installed (Where the Automated tests run in the night), I notice that the file soapui-preferences.xml does not exist. So maybe the solution for the problem is here.
I'm waiting for a time frame to be able to test without impacting testers.
I will keep you posted.
UPDATE 2)
To get rid of this problem I've rebuild my glassfish domain.
Unable to create a branch in subversion using TortoiseSVN.
I get the following error message:
SVN authorization failed: could not authenticate to proxy server: ignored basic challenge, GSSAPI authentication error
Source URL:
"http://svn.lsc.co.uk/svn/projects/CWE/CWEConfig/trunk"
Traget URL:
"http://svn.lsc.co.uk/svn/projects/CWE/CWEConfig/branches/12c"
TortoiseSVN was not passing my credentials to proxy server, hence the request was being blocked there. Supplying credentials in Network > Proxy Settings resolved the issue.
Make sure You have the read/write access for Both trunk and Branch location.
Not able to run any command that requires authentication from keystone, including logging in horizon. Every command fails with below error:
keystone user-list
Authorization Failed: An unexpected error prevented the server from fulfilling your request. (OperationalError) (1045, "Access denied for user 'keystone_admin'#'controllerip' (using password: YES)") None None (HTTP 500)
Please look into keystone log first and see what's the issue brought HTTP 500.
Your keystone database Credentials(user-keystone_admin) may be wrong.Try changing them with the actual database credentials in /etc/keystone/keystone.conf file.
[sql]
connection = mysql://<username>:<password>#<ip>/keystone