Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • J jwt-tokenissuer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • daas
  • jwt-tokenissuer
  • Merge requests
  • !1

The source project of this merge request has been removed.
Merged
Created Oct 03, 2018 by Pål Karlsrud@paalMaintainer

Add the ability to override the client ID which is used as the audience of the JWToken

  • Overview 0
  • Changes 4

Currently, the client ID obtained through the X-Dataporten-Clientid header is always used.

In order to make it easier to associate JWTokens with specific Kubernetes clusters, we want to make it possible to always use a specific client ID as the audience.

This commit allows the admin to use a specific client ID by setting the engine.dataporten.client_id config property. If no client ID is specified, we the X-Dataporten-Clientid header is used.

Edited Oct 03, 2018 by Pål Karlsrud
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master