Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • K kubernetes-gitlab-demo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • kubernetes-gitlab-demo
  • Issues
  • #14
Closed
Open
Created Jan 27, 2017 by Colum McCoole@mccoole

Enable ability to access mattermost API

Thanks for this great implementation. I've been playing around and got most things working.

Specifically, I wanted to test some calls to the mattermost API, such as:

curl -X POST -H "Content-Type: application/json" -d '{"login_id":"gitlab-username","password":"gitlab-password"}' "https://mattermost.k8s.mydomain.com/api/v3/users/login"

But it seems it's not able to reach the API end-point. I'm using the gitlab username and password I set up ... and since I opted to log in to mattermost with these, when enabling mattermost, as per the video, I assumed that these would be right credentials. Also, as per here, I don't think it's necessary to pass a team_id any longer.

{
  "id": "store.sql_user.get_for_login.app_error",
  "message": "We couldn't find an existing account matching your credentials. This team may require an invite from the team owner to join.",
  "detailed_error": "",
  "request_id": "s8zsjyp94ffctbojyqzcq9np9y",
  "status_code": 400
}

From the Headers, it may have something to do with nginx sitting in the middle. Ordinarily, if the step above was successful, the Headers would return a token.

content-length →264
content-type →application/json
date →Fri, 27 Jan 2017 14:51:32 GMT
server →nginx/1.11.3
status →400
strict-transport-security →max-age=15724800; preload
x-request-id →s8zsjyp94ffctbojyqzcq9np9y
x-version-id →3.6.0.3.6.1.d8a78293678fc8c68fbe985f8f83ae7c

If other debugging is happening with the mattermost set-up, as per #11 (closed), then it would be great to get this working too. Thanks.

Assignee
Assign to
Time tracking