It's all about the answers!

Ask a question

Understanding restrictions on synchronizer jazz account

Dave Marsico (4511014) | asked Jun 18 '13, 8:35 a.m.

Would like to understand the rationale behind the statement about the synchronizer jazz account, specifically: "must never be used by a team member to connect to the repository"...  Can anyone elaborate on that restriction??  I can understand why you might not want it to be just any user, but does it need to be absolutely singular of purpose or could it be some generic admin account used by a team for various admin functions???  Some of which might include "connecting" to repository.  Appreciate any additional details/comments.

One answer

permanent link
Ralph Schoon (63.3k33646) | answered Jun 18 '13, 8:41 a.m.
edited Jun 18 '13, 8:41 a.m.
Dave this is because the technical user license that is run for the synchronizer user has capabilities comparable to the to a developer license - it needs read/write access to the SCM system. As far as I am aware, if you used this license for anything other than the context of the synchronizer, especially assign it to a productive user or use it as admin account outside of the context required for the synchronizer, you would be in violation with the license contract.

Dave Marsico commented Jun 18 '13, 10:15 a.m.

Thanks appreciate that clarification

Geoffrey Clemm commented Jun 18 '13, 9:14 p.m.

Also, key CC Synchronizer metadata (such as the CLONE and INTERNAL workspaces) are protected by only allowing the synchronizer account to modify it.  If you let a normal user log in using the synchronizer account, that user can trash the metadata of the synchronized stream.

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.