Open jerneyio opened 5 years ago
Well, in Travis CI we aren't running any integration tests with any OIDC providers. There is a docker compose file in the test
directory, which I use for testing the plugin with Keycloak. There's also a Python script, which configures the plugin on Kong and a OIDC client Keycloak. IMO it should be improved and added to Travis, but I hadn't time to add this.
To use this you would need to start Keycloak and Kong's db, wait till it's ready, run the db migration (uncomment the command
in docker-compose.yml
, start Kong and run setup.py
. The source code in mounted into the container, so you need only to restart Kong's container to test your changes.
Good deal. So I'm not too familiar with Travis CI, but I have been using Docker Compose a lot lately. If I can get this:
To use this you would need to start Keycloak and Kong's db, wait till it's ready, run the db migration (uncomment the command in docker-compose.yml, start Kong and run setup.py. The source code in mounted into the container, so you need only to restart Kong's container to test your changes.
to a point where it's completely automated and kicked off by a single command, would you accept a PR for that? I'll have some free time coming up next week to look into it. I can open up a separate issue for this.
@JoshTheGoldfish, that would be great! :) It would open a possibility to write Selenium/Robot tests and have some integration tests run in the CI. I could handle this afterwards.
@Trojan295 I've created and issue for that here: https://github.com/nokia/kong-oidc/issues/80
lua-resty-openidc supports revocation of the access and refresh tokens as long as a revocation endpoint is exposed and contained in the discovery URL (see: https://github.com/zmartzone/lua-resty-openidc/blob/master/lib/resty/openidc.lua#L1142), so it should be easy enough to extend that support to this project. I'd be happy to submit a PR for this, but testing will be a problem because:
Feel free to correct me on that last point if I'm wrong. If not, I can open up an issue for this as well.