Saving your changes
Be sure to click Update to save any changes to your profile.
Changing your Personal Settings
Personal settings include your Artifactory API Key, password and email address.
You are not able to change your password if Artifactory is configured to use external authentication such as LDAP.
Artifactory allows authentication for REST API calls using your API key as an alternative to your username and password in two ways: you may either using the
X-JFrog-Art-API header with which you can specify an API key , or you may use basic authentication using your username and API key (instead of your password). For more details, please refer to the REST API documentation.
To use your API key for authentication, it must be generated using Artifactory 4.4.3 or later. If generate before, you must regenerate your API key and use the new key as a password for basic authentication.
Creating an API Key
To create an API Key, once you have unlocked your profile, click the "Generate" button next to the API Key field.
Revoking or Regenerating an API Key
Once an API Key is created, it displayed, masked, in the corresponding field. Click the "View" icon to see the API Key in clear-text, or the "Copy" icon to copy the API Key to the clipboard.
To revoke the current API Key, click "Revoke API Key" Note that any REST API calls using the current API key for authentication will no longer be valid.
You may revoke the current API Key and create a new one in a single action by clicking "Regenerate". Any REST API calls using the current API key for authentication will no longer be valid, until you replace the API Key with the new one you just generated.
The following REST API endpoints are available with regard to API Keys:
|Create an API key for the current user.|
|Get the current user's own API key.|
|Revokes the current user's API key.|
|Revokes the API key of another user (requires Admin privileges).|
|Revokes all API keys currently defined in the system (requires Admin privileges).|
Changing Your Password and Email
Once your profile is unlocked, Artifactory displays your password in an encrypted format that can be used whenever you need to provide your password in an environment that is not secure. For example, when making REST API calls over HTTP.
The encrypted password is initially masked, but you may click the "View" icon to view the encrypted password in clear-text. You may also click the "Copy" icon to copy the encrypted password to the clipboard.
To change your Artifactory password, enter your new password and verify it.
You can also modify your email address.
If you forget your password, on the Artifactory Login dialog, select Forgot Password, and enter your username in the following dialog that is displayed.
When you click Submit, Artifactory will send a message to the email address configured for your user account, with a link you can click on to reset your password.
Bintray is JFrog's platform to store and distribute your software libraries. For more details please refer to the
JFrog Bintray Page.
Upon installation, Artifactory has Bintray's JCenter Java repository defined as a remote repository.
You may freely read from JCenter, and other Bintray repositories, however to upload an artifact, or perform other operations on Bintray through Artifactory such as search, you must have a Bintray account and provide your credentials through your profile page.
To provide your Bintray credentials, enter your Bintray Username and the Bintray API Key you received when registering to Bintray into the specified fields in Artirfactory.
To verify that your credentials are valid you can click Test.
From version 4.4, Artifactory supports authentication via SSH for the Git LFS client and the
To be authenticated via SSH, you need to enter your SSH public key in the SSH Public Key (RSA) field.
Binding OAuth Accounts
From version 4.2, Artifactory is integrated with OAuth allowing you to log in through your account with one of the configured OAuth providers. To do so, you need to bind your OAuth account to your Artifactory user by clicking Click to bind next to the corresponding OAuth provider. For more details, please refer to OAuth Integration.