jwt-tokenissuer merge requestshttps://scm.uninett.no/daas/jwt-tokenissuer/-/merge_requests2018-10-03T18:31:27+02:00https://scm.uninett.no/daas/jwt-tokenissuer/-/merge_requests/2Add the initial .gitlab-ci config.2018-10-03T18:31:27+02:00Pål KarlsrudAdd the initial .gitlab-ci config.Makes the necessary changes for the project to be buildable through GitLab CI. The pushing of the Docker image has not yet been tested, but should work in theory :pray: (that part uses basically the same config as daas/appstore-api).
On...Makes the necessary changes for the project to be buildable through GitLab CI. The pushing of the Docker image has not yet been tested, but should work in theory :pray: (that part uses basically the same config as daas/appstore-api).
One of the larger changes is that the package name in the source files has been changed from:
`github.com/uninett/jwt-tokenissuer` to `scm.uninett.no/daas/jwt-tokenissuer`, to reflect the fact that the package is hosted elsewhere now.https://scm.uninett.no/daas/jwt-tokenissuer/-/merge_requests/1Add the ability to override the client ID which is used as the audience of th...2018-10-03T17:19:55+02:00Pål KarlsrudAdd the ability to override the client ID which is used as the audience of the JWTokenCurrently, 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 cli...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.Gurvinder SinghGurvinder Singh