Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin lua-resty-openidc to version 1.6.1 #36

Merged

Conversation

gene1wood
Copy link
Contributor

Workaround lua-resty-openidc bug zmartzone/lua-resty-openidc#249

@gene1wood
Copy link
Contributor Author

gene1wood commented Mar 21, 2019

@gdestuynder I encountered the bug described in zmartzone/lua-resty-openidc#249 in MozDef. I entered the mozilla.oidc.accessproxy docker container and downgraded the module

# opm get zmartzone/lua-resty-openidc=1.6.1
* Fetching zmartzone/lua-resty-openidc = 1.6.1
  Downloading https://opm.openresty.org/api/pkg/tarball/zmartzone/lua-resty-openidc-1.6.1.opm.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 24740  100 24740    0     0  22131      0  0:00:01  0:00:01 --:--:-- 22148
Package lua-resty-http-0.12 already installed.
Package lua-resty-jwt-0.2.0 already installed.
Package lua-resty-session-2.23 already installed.
Package zmartzone/lua-resty-openidc 1.7.0 removed successfully.
Package zmartzone/lua-resty-openidc 1.6.1 installed successfully under /usr/local/openresty/site/ .

I HUP'd nginx and the problem was resolved.

@gdestuynder
Copy link
Contributor

@gene1wood thanks - have you tried their setting idea as well?

@gene1wood
Copy link
Contributor Author

have you tried their setting idea as well?

I've not, maybe after going back to 1.6.1 we can see how to move forward with their idea

@gdestuynder gdestuynder merged commit 4f436d2 into mozilla-iam:master Mar 22, 2019
@gene1wood gene1wood deleted the workaround-lua-resty-openidc-bug branch March 22, 2019 14:51
gene1wood added a commit to gene1wood/MozDef that referenced this pull request Mar 22, 2019
Now that mozilla-iam/mozilla.oidc.accessproxy#36 is merged to master
and built and uploaded to dockerhub as tag `latest` we can go back
to using latest.

Note that in mozilla#1155 I updated the nginx container but missed the nginxkibana
container which should have also been pinned to 8334f96 dockerhub tag
resulting in only one of the two mozilla.oidc.accessproxy containers we
use to work correctly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants