- 03 Oct, 2018 1 commit
-
-
Pål Karlsrud authored
audience of the JWToken. Currently, the client ID obtained through the X-Dataporten-Clientid header is always used. In order to make it easier to associated JWTokens with specific Kubernetes clusters, we want to make it possible to always use a specific client ID as the audience.
-
- 10 Sep, 2018 1 commit
-
-
Gurvinder Singh authored
-
- 17 Aug, 2018 1 commit
-
-
Gurvinder Singh authored
-
- 02 May, 2017 3 commits
-
-
Morten Knutsen authored
-
Gurvinder Singh authored
-
Gurvinder Singh authored
-
- 11 Apr, 2017 4 commits
-
-
Gurvinder Singh authored
-
Gurvinder Singh authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
- 10 Apr, 2017 23 commits
-
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Morten Knutsen authored
-
Gurvinder Singh authored
closes #1
-
- 06 Apr, 2017 1 commit
-
-
Gurvinder Singh authored
-
- 04 Apr, 2017 1 commit
-
-
Gurvinder Singh authored
-
- 03 Apr, 2017 2 commits
-
-
Gurvinder Singh authored
don't encode cert data, as it seems the kubernetes library does that already when writing config file
-
Gurvinder Singh authored
-
- 02 Apr, 2017 3 commits
-
-
Gurvinder Singh authored
-
Gurvinder Singh authored
-
Gurvinder Singh authored
-