User service token instead of provider key in threescale-credentials kubernetes secret (#1717)

This commit is contained in:
Krish 2017-08-09 10:41:51 +02:00 committed by GitHub
parent 1e06bd3aac
commit 3ce4a3d0c3
2 changed files with 2 additions and 2 deletions

View File

@ -223,7 +223,7 @@ you can delete the ``threescale-credentials`` Secret
or leave all the values blank (``""``). or leave all the values blank (``""``).
If you *are* using 3scale, get the values for ``secret-token``, If you *are* using 3scale, get the values for ``secret-token``,
``service-id``, ``version-header`` and ``provider-key`` by logging in to 3scale ``service-id``, ``version-header`` and ``service-token`` by logging in to 3scale
portal using your admin account, click **APIs** and click on **Integration** portal using your admin account, click **APIs** and click on **Integration**
for the relevant API. for the relevant API.
Scroll to the bottom of the page and click the small link Scroll to the bottom of the page and click the small link

View File

@ -110,4 +110,4 @@ data:
secret-token: "<b64 encoded 3scale secret-token>" secret-token: "<b64 encoded 3scale secret-token>"
service-id: "<b64 encoded 3scale service-id>" service-id: "<b64 encoded 3scale service-id>"
version-header: "<b64 encoded 3scale version-header>" version-header: "<b64 encoded 3scale version-header>"
provider-key: "<b64 encoded 3scale provider-key>" service-token: "<b64 encoded 3scale service-token>"