mod_auth_gssapi.git - A GSSAPI based replacement for the aging mod_auth

	Commit message (Collapse)	Author	Age	Files	Lines
*	Unify copyright convention	Robbie Harwood	2016-05-18	1	-1/+1
\| \| \| \| \|	Signed-off-by: Robbie Harwood <rharwood@redhat.com> Reviewed-by: Simo Sorce <simo@redhat.com>
*	Optimize BASIC AUTH checks with sessions.	Simo Sorce	2015-06-13	1	-0/+1
\| \| \| \| \| \| \| \|	If sessions are enbled store a MAC of the password and use it to check if the password is the same on follow-up requests. If it is, avoid the whole gssapi dance and use the session data instead. Signed-off-by: Simo Sorce <simo@redhat.com>
*	Split HMAC_BUFFER out as a separate publi function	Simo Sorce	2015-06-13	1	-0/+2
\| \| \| \|	Signed-off-by: Simo Sorce <simo@redhat.com>
*	Add permanent session keys support	Simo Sorce	2014-07-10	1	-1/+2
\| \| \| \| \| \| \| \| \|	Keys (encryption+MAC) can now be stored in apache configuration. The key must be a base64 encoded blob of original length of 32 bytes (16 bytes for encryption and 16 for the MAC key) The format is: key:<base64 blob>
*	Add mod_session support	Simo Sorce	2014-07-10	1	-0/+17
	By setting GssapiUseSessions we enable the module to store a bearer token with the user and gss names in the client, this way we can allow clients to perform authentication once but then remain authenticaed for the duration of the session or until the original credentials expire. The Secure cookie used to store the token is encrypted using a randomly generated AES key at process startup. This means multiple apache servers will not be able to use the same cookie, however the client will reauth transparently if the cookie cannot be read.