> When shibboleth can be used from backend activities like SVN/GIT.
> Realtime Example is
> 1. User tried to check in files in some SCM repos like SVN or GIT
> 2. This should take the user to Shibboleth (IdP) where the Shibboleth
> should prompt for username and password in the command prompt (shell
> itself) and not in UI
> 3. When the credentials are correct, a positive sign like 'true' should be
> sent to the SVN call
> 4. Then the SVN operation will be carried out.
Passwords suck, and entering passwords for each `svn up` or `git push`
or whatever sucks even more. So if the end results sucks I wouldn't
bother investing any effort into getting there.
Instead just use some Shib-protected web UI that allows people to
upload their SSH public key, then use SSH with keys only to access the