We now have an SSO and identity management solution available that works with both Confluence and JIRA. It's called Crowd, and you can find more information here:

http://www.atlassian.com/software/crowd

While you're at it, if you could work out a way to include https in the single sign-on party, that would be most wonderful. In other words, once a user has logged in to https, that user and group should be automatically accepted as the signon for J & C.

Somewhat related, please realize Confluence doesn't even currently do single sing-on with itself, as is clearly demonstrable by trying to utilise Confluence-generated RSS feeds from within Confluence when anonymous access is forbidden...

Is there a roadmap for this feature? It would really be nice, to know when this feature could become real at least.

CONF-1595 tries to describe this same issue...

Trackback spam links removed from issue.

Thanks, Sam. I've removed the spam for now.

It comes back frequently, and we don't yet have a very effective way of dealing with it, other than manual deletion.

Full support for this. The security holes in Jira/Confluence integration are gaping. This isn't exactly a stopper to our corporate adoption of the tools, but it makes doing what we want to do a lot harder.

For ref I was linked here from CONF-2711.

This would be fantastic. I just can't bring myself to put a username/password in a URL.

See also CONF-4744, which is about the problem of trackback not working for non-anonymous htts - also some kind of login problem...