Closed knowings closed 5 years ago
@knowings thanks for reporting this.. I guess that you managed to solve this one. Our experience with Postman is that these collections go out of sync quite fast. Please report issues in the main Activiti/Activiti repo next time so we can answer fast.
@salaboy the main issue lies in how the full example can be used in a docker-for-desktop k8s cluster. I used an Ingress like "activiti-keycloak.127.0.0.1.nip.io" and it's not a good idea within the cluster... I talked about it in gitter with people that helped me to start working on a solution (WIP BTW). Next time, I will report on the main repository ;)
@knowings we will definitely appreciate if you found the fix for that to contribute it back to our gitbook. Is that something that you think that you can do?
After setting up (locally) Activiti Cloud Full Example on the kubernetes cluster provided by Docker, I run the Test User case suite and got strange results: despite green results, only the getKeycloakToken pass with a 200 HTTP status, but the following requests fails with a 401 HTTP status code.
From the logs of activiti-cloud-gateway I found:
And from the logs of activiti-keycloak I found:
Obviously, something went wrong but what ?
The tests results: Test User case.postman_test_run.zip