Replies: 2 comments 1 reply
-
ping any news on this question? |
Beta Was this translation helpful? Give feedback.
-
Well the problem is that there is nothing that is doing the actual delegation. The support in mod_auth_gssapi is written from the pov of an application that does something and then uses delegated credentials to access some other resource. It is not written for a proxy situation where nothing happens on the proxy itself except authentication. In order to work in the proxy case we'd have to grow an additional option to have mod_auth_gssapi initialize a session with the target of the proxy. There are challenges here though. First of all only one shot session setups will probably work, because mod_auth_gssapi would not be invoked (normally) if the target server returns a GSS_S_CONTINUE_NEEDED error instead of GSS_S_COMPLETE. It is also not clear to me that we can add authorization headers to the proxy outgoing call, that may require additional configuration that copies some variables that mod_auth_gssapi sets. I have not looked into this scenario before, so it is unclear how much can be mad to work for the proxying case. |
Beta Was this translation helpful? Give feedback.
-
I have a PHP webapp running behind a reverse-proxy that I would like to authenticate users based on their ticket.
The user and both apache application have accounts in the AD-domain (example.com), which runs on Samba (4.16)
When no authentication is setup on the revproxy, the user ticket is sent to
HTTP/[email protected]
is sent straight to the webappserver.Obviously the webserver is not able to decrypt the ticket and returns an error:
Now when I add mod_gssapi with s4u2proxy on the revproxy server like this:
The keytab
/etc/keytab/svc_revproxy_apache.keytab
containsHTTP/[email protected]
The account
svc_revproxy_apache
is configured to allow constrained delegation tosvc_webapp_apache
(which is the account used by the backend webapp server)When I connect to the revproxy server as user1, I see a file
[email protected]
getting stored in/run/apache2/krb5_delegation_ccache
, which tells me that the interaction with the KDC works as expected. The traffic is forwarded to webapp.example.com but the ticket never gets proxied / changed by s4u2proxy and hence it reaches the webapp server asHTTP/[email protected]
resulting in the same error as shown above.What is it I am doing wrong here?
Beta Was this translation helpful? Give feedback.
All reactions