// Module included in the following assemblies:
//
// * cicd/jenkins/images-other-jenkins.adoc

:_content-type: PROCEDURE
[id="images-other-jenkins-cross-project_{context}"]
= Providing Jenkins cross project access

If you are going to run Jenkins somewhere other than your same project, you must provide an access token to Jenkins to access your project.

.Procedure

. Identify the secret for the service account that has appropriate permissions to access the project Jenkins must access:
+
[source,terminal]
----
$ oc describe serviceaccount jenkins
----
+
.Example output
[source,terminal]
----
Name:       default
Labels:     <none>
Secrets:    {  jenkins-token-uyswp    }
            {  jenkins-dockercfg-xcr3d    }
Tokens:     jenkins-token-izv1u
            jenkins-token-uyswp
----
+
In this case the secret is named `jenkins-token-uyswp`.

. Retrieve the token from the secret:
+
[source,terminal]
----
$ oc describe secret <secret name from above>
----
+
.Example output
[source,terminal]
----
Name:       jenkins-token-uyswp
Labels:     <none>
Annotations:    kubernetes.io/service-account.name=jenkins,kubernetes.io/service-account.uid=32f5b661-2a8f-11e5-9528-3c970e3bf0b7
Type:   kubernetes.io/service-account-token
Data
====
ca.crt: 1066 bytes
token:  eyJhbGc..<content cut>....wRA
----
+
The token parameter contains the token value Jenkins requires to access the project.
