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

Support POST API requests? #8

Open
alerque opened this issue Apr 30, 2021 · 5 comments · May be fixed by #13
Open

Support POST API requests? #8

alerque opened this issue Apr 30, 2021 · 5 comments · May be fixed by #13

Comments

@alerque
Copy link

alerque commented Apr 30, 2021

I was trying to set this up to authenticate against Keycloak's token endpoint and discovered that it seems to be hard coded to use GET requests w hile the API I have requires the secrets be passed in POST data. I can construct a working query via curl that returns something I think will be processed okay, but when I setup PAM to do the same thing with this module I can only figure out how to get a GET request out.

Comments in #3 which also mentions Keycloak suggest using a different project pam-exec-oauth2 which seems to send POST requests correctly. I going to try setting up that for now, but I would rather switch back to this if a way to authenticate against Keycloak was added.

By the way, I did setup Arch Linux packaging on the AUR for this if anybody wants it.

@CyberDem0n
Copy link
Owner

I think one of the existing forks already supports it: https://github.com/WLOGSolutions/pam-oauth2

@alerque
Copy link
Author

alerque commented Apr 30, 2021

Hmm, that does look promising. The documentation is dicy but it looks like it might handle the request.

Would you accept a PR with that change if I cleaned it up a bit? It would be nice to get document working Keycloak support in a tagged release.

@azmeuk
Copy link

azmeuk commented Sep 15, 2021

@alerque per chance did you have some time to spend on a patch?

@alerque
Copy link
Author

alerque commented Sep 20, 2021

No I haven't gotten a chance to invest back in this. I am still using pam-exec-oauth2 in production as was my temporary resolution above. I could potentially put it back on my todo list, but not having an answer from the maintainer as to whether that change would even be accepted is not exactly encouraging.

@azmeuk
Copy link

azmeuk commented Sep 20, 2021

@CyberDem0n what do you think?

@Maxime2 Maxime2 linked a pull request Apr 16, 2024 that will close this issue
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 a pull request may close this issue.

3 participants