|
Important
|
Before Start
You should have NO virtualservice, destinationrule, gateway or policy (in ./scripts/clean.sh |
In this chapter, we are going to see how to enable authenticating end user with Istio. At the time of writing this chapter, only the JWT mechanism is supported.
To use JWT end-user authentication, we need a JWT issuer. In this case, we are going to use Keycloak but notice that any other one is valid as well.
Before starting let’s deploy Keycloak in our tutorial namespace.
oc apply -f keycloak/Deployment.yml -n tutorial
oc create -f keycloak/Service.yml -n tutorial
oc expose service keycloakNow we need to configure Keycloak with realms, users, passwords, roles …
So open Keycloak administration web page by opening a browser to http://keycloak-tutorial.192.168.64.87.nip.io/ where the IP should be minishift IP (minishift ip).
Then select administration console option and use admin/admin as login/password.
And you’ll get something like:
Then create a new realm. Just move the pointer over Master section which is found in upper-left section and click on Add realm button.
Then create a realm called istio.
Inside istio realm create a public client ID called customer-tutorial.
|
Important
|
It is really important that the client id is set to customer-tutorial because it is used as allowed audiences in the mesh.
|
Create a role user.
And finally, create a user called demo under the previous role.
Select the role from Availavle Roles section and push Add selected.
Then go to Credentials and set demo as the password.
Finally, go again to Details tab and in Required User Actions input, remove the Update Password action.
And finally push Save button.
Now it is time to enable end-user authentication.
The first thing you need to do is run curl customer-tutorial.$(minishift ip).nip.io and validate that now it is still possible to communicate between all services without been authenticated.
curl customer-tutorial.$(minishift ip).nip.io
customer => preference => recommendation v1 from 'b4d67bcb7-7rp88': 4After that open the file istiofiles/enduser-authentication-jwt.yml and replace the IP of fields issuer and jwksUri by your minishift IP (minishift ip).
spec:
origins:
- jwt:
issuer: "http://keycloak-tutorial.192.168.64.87.nip.io/auth/realms/istio"
jwksUri: "http://keycloak-tutorial.192.168.64.87.nip.io/auth/realms/istio/protocol/openid-connect/certs"
audiences:
- customer-tutorial
principalBinding: USE_ORIGIN
And then run:
istioctl create -f istiofiles/enduser-authentication-jwt.ymlThen let’s run the curl again:
curl customer-tutorial.$(minishift ip).nip.io
Origin authentication failed.%`And now the communication is not possible because the user has not been identified (provides a valid JWT token).
To get a correct token, just run next curl request.
curl 'http://localhost:8080/auth/realms/istio/protocol/openid-connect/token' -d 'username=demo&password=demo&grant_type=password&client_id=customer-tutorial'And set the content of attribute access_token into token variable in your terminal.
If you want to see what is inside the token just go to jwt.io in Debugger section and paste the token.
Notice how aud field is set to customer-tutorial.
token="eyJhbGciOiJSUzI1NiIsInR5cCIg....."
curl -H "Authorization: Bearer $token" customer-tutorial.$(minishift ip).nip.io
customer => preference => recommendation v1 from 'b4d67bcb7-7rp88': 4Now just change some part of the token and send the request again, you’ll notice that request is refused.
|
Important
|
In this chapter you’ve seen how to enable end-user authentication with JWT. Obviously, you should also enable mTLS to avoid any attacker could take the token. Check mTLS section to learn more about mTLS and Istio. |







