Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38518

Add ability to specify Mattermost user login credentials

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: mattermost-plugin
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Attachments

        Activity

        Hide
        rmyung Roger Myung added a comment -

        Having learned a little more about mattermost authentication, I think OAuth support would solve the authentication problem.

        Show
        rmyung Roger Myung added a comment - Having learned a little more about mattermost authentication, I think OAuth support would solve the authentication problem.
        Hide
        jovandeginste Jo Vandeginste added a comment -

        My apologies for the late answer; I read and re-read your issue, but I fail to understand... (I don't really use Windows for servers, so I have no experience at all). Is the connection between Jenkins and Mattermost not via the REST API (and thus entirely userless)?

        Show
        jovandeginste Jo Vandeginste added a comment - My apologies for the late answer; I read and re-read your issue, but I fail to understand... (I don't really use Windows for servers, so I have no experience at all). Is the connection between Jenkins and Mattermost not via the REST API (and thus entirely userless)?
        Hide
        rmyung Roger Myung added a comment -

        I'm not sure the connection between mattermost and Jenkins works, I have not looked at the plugin source. A REST API would not be userless though, it would use http authentication.

        The errors I see in the Jenkins logs are :
        Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials
        org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials

        Show
        rmyung Roger Myung added a comment - I'm not sure the connection between mattermost and Jenkins works, I have not looked at the plugin source. A REST API would not be userless though, it would use http authentication. The errors I see in the Jenkins logs are : Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials
        Hide
        jovandeginste Jo Vandeginste added a comment -

        It is userless in the sense that it uses an api token as part of the url (so not even BASIC AUTH); the endpoint url has the following form:

        http://your.mattermost.domain.example.com/hooks/alfanumerictoken

        Since I know very little about the subject, I just googled around a bit and found this explanation about a similar issue. Could you have a look if it is at all relevant to your case or not?

        Show
        jovandeginste Jo Vandeginste added a comment - It is userless in the sense that it uses an api token as part of the url (so not even BASIC AUTH); the endpoint url has the following form: http://your.mattermost.domain.example.com/hooks/alfanumerictoken Since I know very little about the subject, I just googled around a bit and found this explanation about a similar issue. Could you have a look if it is at all relevant to your case or not?
        Hide
        rmyung Roger Myung added a comment -

        Thanks, it turned out to be a proxy issue

        Show
        rmyung Roger Myung added a comment - Thanks, it turned out to be a proxy issue

          People

          Assignee:
          jovandeginste Jo Vandeginste
          Reporter:
          rmyung Roger Myung
          Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

            Dates

            Created:
            Updated:
            Resolved: