this step is no logner needed since jwks can be retrived with jwks_fe…

…tcher config (#238)

Signed-off-by: huabing zhao <[email protected]>

bookinfo-example/README.md

@@ -39,7 +39,7 @@ URI to be hosted on a protected endpoint.
    ```shell
    kubectl edit cm -n istio-system
    ```
-   
+
    Change the mesh config with the config below.
 
    ```yaml
@@ -54,15 +54,6 @@ URI to be hosted on a protected endpoint.
 
    Alternatively you can install Istio with a sample [operator.yaml](https://github.com/istio-ecosystem/authservice/blob/master/bookinfo-example/authservice/istio-operatory.yaml) we provide when using `istioctl install -f istio-operator.yaml`.
 
-1. Fetch the identity provider public key and populate into the configmap. In our example, run
-`scripts/google-jwks.sh`.
-
-      ```shell
-      bash scripts/google-jwks.sh
-      ```
-   Copy the output JWK (with escape) literally to the [templates/config.yaml](https://github.com/istio-ecosystem/authservice/blob/master/bookinfo-example/authservice/templates/config.yaml#L30)
-   to replace the JWK content.
-
 1. If you are using a Google account as your Identity Provider, you need to specify
 the following redirect URL for the client ID you are using. In this example,
 it would be `https://localhost:8443/productpage/oauth/callback`.

bookinfo-example/authservice/values.yaml

@@ -1,5 +1,5 @@
 authservice:
-  image: ghcr.io/istio-ecosystem/authservice/authservice:0.4.1
+  image: ghcr.io/istio-ecosystem/authservice/authservice:0.5.3
   # How the authservice will be enabled and enforced.
   # This can be at ingress (by default) or at application sidecar.
   enforcingMode: ingress