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

Fill in $remote_user #1

Open
hazcod opened this issue Jul 20, 2015 · 10 comments
Open

Fill in $remote_user #1

hazcod opened this issue Jul 20, 2015 · 10 comments

Comments

@hazcod
Copy link

hazcod commented Jul 20, 2015

Is it possible to fill in $remote_user with the username of the authenticated user?
This so I can correctly process my access logs.

Temporary workaround is described here; samizdatco#22

Thank you

@erikdubbelboer
Copy link

As you can see in the function that calculates $remote_user ngx_http_variable_remote_user() it uses ngx_http_auth_basic_user() which is a core function which parses the authentication header but only supports Basic. A patch to nginx is required. I'll see what I can do when I have some time but I guess it will also take some time to be put in an nginx release.

@hazcod
Copy link
Author

hazcod commented Jul 21, 2015

Ok, thank you.
I am using the workaround successfully for now.

@SubrataM3
Copy link

@erikdubbelboer
Is this issue fixed ? it is still not working for me.
I have compiled this module as dynamic module with nginx version: nginx/1.16.0 .

Please let me know.
OP's solution works for me though, but this should be inbuilt within module.

@erikdubbelboer
Copy link

@SubrataM3 I'm afraid this has not been fixed seeing as my patch to nginx was never accepted: http://mailman.nginx.org/pipermail/nginx-devel/2015-August/007209.html

@SubrataM3
Copy link

@SubrataM3 I'm afraid this has not been fixed seeing as my patch to nginx was never accepted: http://mailman.nginx.org/pipermail/nginx-devel/2015-August/007209.html

Oh, that's bad. is it possible to bump that topic?

@erikdubbelboer
Copy link

A new attempt would have to be made. Seeing the last one was from 2015. But seeing as not a single person responded to me last time I'm not really encouraged to try again. I don't feel like the nginx maintainers are interested in patches like this.

@SubrataM3
Copy link

A new attempt would have to be made. Seeing the last one was from 2015. But seeing as not a single person responded to me last time I'm not really encouraged to try again. I don't feel like the nginx maintainers are interested in patches like this.

Yep, I understand that, but since no one explicitly denied the patch i think you should try once more. digest auth is a basic feature and only your module supports it. That patch would be beneficial to many users. :-)

@erikdubbelboer
Copy link

I'm sorry but I really don't have the time for this at the moment. Could you maybe try to submit a patch to nginx?

@SubrataM3
Copy link

Hi,
I can do that, but if they starts some discussion or ask question i won't be able to answer since i don't have any knowledge about nginx codebase .

@erikdubbelboer
Copy link

When that happens I'll help you answer any question.

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

No branches or pull requests

3 participants