Authentication

All requests to the Proxy must be authenticated using HTTP Basic Authentication over HTTPS. Credentials are provisioned by your Lineaje platform administrator and stored as a Jenkins (or CI system) credential referred as ARTIFACTORY_CREDS in below examples.

Credential format: username : password/token pair, base64-encoded in the Authorization header. When configured correctly, is handled automatically by Maven, pip, and npm.

Creating ARTIFACTORY_CREDS in Jenkins

1. Generate a Lineaje CLI Personal Access Token in Lineaje Portal

   1. Go to https://app.veedna.com/ and log in with your credentials.

   2. From the left navigation panel, navigate to: Integrations → Deploy on Private Cloud → Lineaje CLI Personal Access Token

   3. Click Generate Token.

   4. You will be redirected to a new page where you will need to:

      1. Authenticate again using your credentials.

      2. Grant the required permissions.

   5. Once the authentication is completed, return to the previous browser tab.

   6. Copy the Personal Access Token (PAT) and store it securely. This token will be used when configuring credentials in Jenkins.

2. Add the Personal Access Token to Jenkins (Follow similar steps for CI of your choice)

   1. Open Jenkins and navigate to: Manage Jenkins → Credentials

   2. Under Stores scoped to Jenkins, select System.

   3. From the left-hand menu under System, click Global credentials (unrestricted) to open the default domain. Credentials can also be configured at the folder level if more granular access control is required.

   4. Click Add Credentials from the left-hand menu.

3. Configure the Credential

   1. Fill in the following fields

      1. Kind: Username with password

      2. Username: Enter your email configured on Lineaje Platform

      3. Password: Paste the Personal Access Token (PAT) generated earlier

      4. ID: Provide a meaningful identifier (this ID will be used to reference the credential in Jenkins jobs and pipelines). If the ID field is left empty, Jenkins will automatically generate a unique ID.

      5. Description: Add a description for easier identification

   2. Click Create to save the credential.

4. Using the Credential in Jenkins Pipelines

   After creating the credential, it can be referenced in Jenkins jobs or Jenkinsfile pipelines using the Credential ID specified during creation.

Referencing Credentials in a Jenkinsfile

In the Jenkinsfile, use the credentials block to expose the username and password as environment variables:

ARTIFACTORY_CREDS = credentials(‘<ID>’) 
Username and Password are now available in environment as ARTIFACTORY_CREDS_USR, ARTIFACTORY_CREDS_PSW 

Maven Integration