Not only would it be convenient -
It would also prevent your credentials from going over the wire in plain text, an obvious security concern.
I echo this request.
Also this is a dupe of 1616

I absolutely agree that this is a necessary feature. Although we run jenkins on SSH which at least means that credentialls are not being passed in plain text. But setting up ssh properly is a real pain and it is still not desireable to have users typing in their AD credentials to access Jira when they are already logged on to a machine in the domain.

If your Jenkins instance runs on Tomcat and uses Atlassian Crowd as its user management system, you can provide your Jenkins users with Integrated Windows Authentication with the following add-on: https://marketplace.atlassian.com/plugins/com.cleito.iwaac

bruno_vincent, that is not really a solution. The plugin is $10 per user. That is expensive.
Tomcat itself can be configured to support Windows Authentication. How difficult would it be to tell Jenkins to use authentication context from tomcat?

Most but operate Jenkins with Jetty.

Ok, but Jetty can also be configured with SPNEGO http://www.eclipse.org/jetty/documentation/current/spnego-support.html .
How far is configuring SPNEGO in Jetty from getting implicit Windows Authentication in JENKINS ?

jcztery, price is always subjective but if you keep in mind that you can use the same plugin on all your Atlassian products (Jira, Confluence, Bamboo, Bitbucket, FishEye/Crucible) and custom web applications that use Crowd as their user management system, it's probably not that expensive. By the way, the add-on can be deployed on both Tomcat and Jetty.