Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: mattermost-plugin
-
Labels:None
-
Environment:The plugin seems to take the login information from the Jenkins user. This is major limitation on Windows since Jenkins uses the Active Directory login, but Mattermost can only use Active Directory if you use Mattermost Enterprise. That means this plugin can only be used on Windows with Mattermost Enterprise.
The plugin seems to take the login information from the Jenkins user. This is major limitation on Windows since Jenkins uses the Active Directory login, but Mattermost can only use Active Directory if you use Mattermost Enterprise. That means this plugin can only be used on Windows with Mattermost Enterprise.
-
Similar Issues:
Attachments
Activity
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)?
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
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
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?
Thanks, it turned out to be a proxy issue
Roger Myung
added a comment - Thanks, it turned out to be a proxy issue 
Having learned a little more about mattermost authentication, I think OAuth support would solve the authentication problem.