Comments

  • Bil Simser
    posted August 21, 2008 in Go > Troubleshooting

    FWIW, after talking to Bobby it seems https with subversion is a problem for Cruise. We’ve switched over to http so it works fine now.

  • Bil Simser
    posted August 5, 2008 in Go > Troubleshooting

    @Derek

    I went through the steps you mentioned. By default (at least according to the config file) store-auth-creds is defaulted to yes. I changed the file to be explicit.

    The cache contained certificates for my svn server url so that was fine.

    Still fails with the authorization message.

    I’ll maybe come back to this another day, I’ve already spent too much time trying to get it running in our environment now and have no success. Maybe I’ll try to get a sandbox running in isolation, but that’s really not going to help me much.

    Thanks.

  • Bil Simser
    posted August 4, 2008 in Go > Troubleshooting

    @Chris: I have this already in my svn section:

    <svn username="cruise" url="https://server:8443/svn/project/trunk/" password="cruise" />

    The problem is that “cruise” isn’t a machine account, it’s a svn account so I can’t login and store any credentials. The service is running under a domain account which I can login as. Not sure how to resolve this?

  • Bil Simser
    posted June 17, 2008 in Mingle > General Discussion

    @Jonathan: I’m working on a Visual Studio plugin which provides read-only access to cards in projects. Not sure what you’re referring to as far as SCM plugins since Mingle isn’t a source control system. If you’re talking about having Mingle show commits from TFS (like how it does with Subversion) then my plug-in won’t help.

  • Bil Simser
    posted May 8, 2008 in Mingle > API

    Bruno,

    Thanks for the link and example. For whatever reason I still cannot get it to work in the client environment. Something is screwy here and I don’t think I can get any rest api calls to work (except in the browser directly). Code just doesn’t work for me as I always get a 401 error back.

  • Bil Simser
    posted May 5, 2008 in Mingle > API

    More information. Turns out that I’m using IE6 and they’ve disabled the username:password@server syntax with a security patch some time ago. Unfortunately I don’t have access to anything but IE6 for testing right now (so FF or something is a problem).

    I did find a registry hack to remove this behavior and just trying to get the link working in the browser first. I still think there’s something wrong in the Mingle API to get this working. For example, I’m trying to run against my own local install (localhost) on port 8080 with non-LDAP authentication (Mingle is keeping track of usernames and passwords).

    Here’s the request when I use the username:password@server:port syntax in my browser:

    GET /projects/test/cards.xml HTTP/1.1
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, application/x-silverlight, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, application/x-silverlight-2-b1, /*
    Accept-Language: en-ca
    Accept-Encoding: gzip, deflate
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648)
    Host: localhost:8080
    Proxy-Connection: Keep-Alive
    Cookie: last-visited-project=brms; MINGLE20SESSIONID=1kzb9dfuh9meb; _session_id=e19df056d9eb37d38f87f49e23f73657

    And here’s the response:
    HTTP/1.1 401 Unauthorized
    Content-Type: application/xml; charset=utf-8
    Set-Cookie: _session_id=e19df056d9eb37d38f87f49e23f73657; path=/
    Cache-Control: no-cache
    Content-Length: 32
    Server: Jetty(6.1.5)

    Incorrect username or password.

    I know I’m using the correct username/password here (typed it into the login form).

    Is it possible Mingle cannot handle the username:password url *and a specified port number? Or maybe this just won’t work in IE6 no matter what?

  • Bil Simser
    posted May 5, 2008 in Mingle > API

    @LiXiao: Sorry, I did mean to use the full URL in the original message, just figured I didn’t have to spell everything out.

    I’m giving up on trying to get LDAP and the REST API to work as I just can’t get it to work. I’ve got the configuration you mentioned and restarted the server.

    I’ve entered this in my browser (IE6):
    http://[username]:[password]@[server]:[port]/projects/test/cards.xml

    Where [username] is my username (I’ve signed out of Mingle previously and opened a new browser session). This is my username without the domain prefix, same as what I sign into the Mingle login page with.

    I can’t tell what error is coming back. I get a title bar of “Invalid syntax error” and some text on the page that says “The page cannot be displayed” and “The page you are looking for might have been removed or had its name changed”

    At this point I’m only going to provide support for my plugin for non-LDAP setups until someone can get me information that works in my test setup. Problem is there’s no information Mingle is providing me to help diagnose the problem.

    Thanks.

  • Bil Simser
    posted May 3, 2008 in Mingle > API

    One more thing, if I sign out of Mingle and enter this into the browser:

    http://[server]:[port]/projects/[project]/cards.xml

    Using fiddler I see this header come back (using IE6):

    HTTP/1.1 401 Unauthorized
    Content-Type: application/xml; charset=utf-8
    Set-Cookie: _session_id=4eb2940600bcc00be22ffc975514cddf; path=/
    Cache-Control: no-cache
    Content-Length: 32
    Server: Jetty(6.1.5)

    Incorrect username or password.

  • Bil Simser
    posted May 3, 2008 in Mingle > API

    I have basic_auth_enabled: true in my config file, but I’m looking up users via LDAP so that’s configured as well (and working).

    If I try the http://[user]:[password]@[server]:[port] in my browser (after signing out of Mingle) I just get a blank page (I’m assumine a 401 or 500 error)

    CredentialCache.DefaultCredentials just grabs the credentials from the current user signed into the OS and uses it.

    The syntax you listed doesn’t work and results in a 401 (unauthorized) error.

    For the life of me, I cannot figure out how to do this with a LDAP integrated setup (Mingle users/passwords works fine) and it’s highly frustrating.

  • Bil Simser
    posted May 3, 2008 in Mingle > API

    Thanks. Is it a feature I should request or is it just something that’s already planned?

  • Bil Simser
    posted April 29, 2008 in Mingle > API

    The api states it only supports basic authentication and you have to turn it on. We’re running in using LDAP authentication so is there a way to do mixed? Are we not going to be able to use the API if we have LDAP authentication turned on and have to let users manage passwords?

  • Bil Simser
    posted April 17, 2008 in Mingle > Bug Reports

    Watch for it on CodePlex, my second home.

  • Bil Simser
    posted April 17, 2008 in Mingle > Bug Reports

    Yeah, there are a few places in the docs where I had to crank up my install and poke around to find the right path. I just chalked it up to beta docs and moved on (building a Mingle plug-in for Visual Studio). Hopefully the API will be posted soon with these fixes!

  • Bil Simser
    posted April 17, 2008 in Mingle > General Discussion

    Thanks David. Didn’t know that existed (although I haven’t read every page in the help system). Didn’t see it in the help tree so maybe it needs better visibility?

    Is there a list of any other Special: pages in the system? I can’t get a result here if I search for “Special:” (and “Special” brings back too many results).

    Thanks.

  • Bil Simser
    posted April 16, 2008 in Mingle > Feature Requests

    How is this implemented? I’m not seeing where you can do this?