The current way of authentification for external references in a project is not clear.
See the extended discussion in JENKINS-22542
We specify Credentials to use for check out. With these credentials you have complete (read-only) access to the project and its externals. (project and externals are in the same repository).
Why do we need to specify these same credentials again just to get the change log?
For security? but the check out is already successful.
Dave (our evil developer) can add an external to SecretProjectC to projectA.
Dave can no longer do a complete checkout locally as he has no access to projectC.
When the build server has access (svn user Jenkins with global read only access)
Now the build server can access SecretProjectC (because another external in projectA requires the additional credentials).
So you rely on having configured exluded svn user Jenkins from secret projects.
In which case the checkout already fails, as this requires additional credentials which Dave (hopefully) cannot configure in the build server.
I suggest to
1: remove the need for additional credentials when all items in a project require the same credentials.
2: Make he selection of credentials a drop down without the need to type the realm (as the realm is already encoded in the credentials.
Edit: second option removed as the 'encoded realm' is only a comment