It's all about the answers!

Ask a question

Receiving CRJAZ0218I Not logged in to the repository When adding link as 'Affected by Defect'

Omar Jimenez (112) | asked Jun 16 '16, 11:02 a.m.
I'm working with RTC v6.0.1 and after I've created a Defect, Sotry, Task, etc.. WorkItem then try to add Link Affected by Defect, Contributes to, Add Tracks or Affects Plan Item I'm getting the error: "Not logged in to the repository.ID CRJAZ0218I"
I've followed the next notes in order to get it done,
But the same problem persist.
Any clues about this "Not logged in" exception?

Donald Nong commented Jun 17 '16, 1:38 a.m.

The documents talk about a "remote repository". What is this repository in your environment? It seems that you happen to have the same login ID in both repositories but the SSO does not work, or an Authorization Required window should pop up but does not do so.

Omar Jimenez commented Jun 20 '16, 10:15 a.m.

Thanks for your input Donald, I'll take a look into application server configuration

2 answers

permanent link
Ralph Schoon (63.2k33646) | answered Jun 20 '16, 10:47 a.m.
All the links mentioned in the question above are CLM links. See
These links are specifically used to link items across application, repository and project area boundaries.
Please read and the link above.

If you work with multiple applications/repositories you would have to be connected to these repositories.
In addition, as far as I am aware, the repositories would have to be registered to the same JTS, or the applications would have to be set up as friend.
Last but not least, the consumer provider relationship between the project areas, where you want to create the link must be set up.

However, assuming you did all that and you where actually able to select the other end for the relationship, the message is disturbing, as you would have already been logged in to select the other end work item.

permanent link
Isabel Murakami (3811615) | answered Oct 30 '16, 10:50 a.m.
I have worked on a similar issue - Contributed to and Tracks links were receiving CRJAZ0218I after upgrade to 6.0.x, and it was caused by a defect recently identified for 6.0.x.
Avoid setting the Jazz Authentication token expiration time value to -1
Check if your (all apps) are using
So workaround is to change it back to the default, which is 21600 seconds, or change to any other number except -1.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.