If I have it set up so you have to be logged in via MT or TypeKey to leave a comment, I run into an odd situation when I try to leave comments on my own blog. It'll recognize me and say "welcome back Derek", etc., but if I try to leave a comment it tells me I must be signed in to leave a comment. Invariably what I find is that I'm logged in via TypeKey (with username 'foo') and also logged in via MT (with username 'foo') then it complains. If I "log out", and then log back in (only with one, usually MT authentication), then the comment (usually) goes through.

It seems like MT is getting confused about "how I'm logged in" and starts to freak out because I'm got two potential login paths with the same username (through different authentication-domains, so that *should* be absolutely fine)... but apparently it's not....

Thoughts?

I seem to have a similar bug - I have commenting set so you can either use Typekey or OpenID, or you can comment anonymously. When I go to leave a comment on an entry, it gives me a "Thanks for signing in, Alden" message, but when I post the comment, it comes up as "Anonymous". I suspect what's happening is that because I don't have MT account commenting turned on, it's rejecting my it. OpenID commenting works fine.

Alden

I think this is where the domain in the CGIPATH is different to the domain you are accessing MT through, so the authentication cookie has a different server name.

In my case, the MT cgi is on the same domain as the blog, so this shouldn't be an issue.

Alden

What ONM is describing is a bit more specific than that. There are some problems caused by having CGIPath set to domain.com but accessing MT via www.domain.com due to the AJAX usage.