On 09/13/2018 04:15 PM, Andrea Aime wrote:
> Hi Richard,
> did you try using the monitoring module, in "audit" mode? It will logs
> all sorts of details about the requests
> you're getting, regardless if they are post or get, including the
> username (but I don't know if it works
> fine with LDAP a
Hi Richard,
did you try using the monitoring module, in "audit" mode? It will logs all
sorts of details about the requests
you're getting, regardless if they are post or get, including the username
(but I don't know if it works
fine with LDAP auth).
See:
http://docs.geoserver.org/latest/en/user/ex
Hi Richard
I log the HTTP header Authorization in Tomcat/HAProxy/Apache and this will
give you the base64 username:password that you see in WireShark, etc.:
Tomcat/Apache:"%{Authorization}i"
HAProxy:
capture request header Authorization len 50
log-format "... %{+Q}hrl ..."
I'm not
On 09/13/2018 11:48 AM, Peter Smythe wrote:
> Hi Richard
>
> I log the HTTP header Authorization in Tomcat/HAProxy/Apache and this
> will give you the base64 username:password that you see in WireShark, etc.:
>
> Tomcat/Apache: "%{Authorization}i"
>
> HAProxy:
> capture request header Au
Hi Richard
I log the HTTP header Authorization in Tomcat/HAProxy/Apache and this will
give you the base64 username:password that you see in WireShark, etc.:
Tomcat/Apache:"%{Authorization}i"
HAProxy:
capture request header Authorization len 50
log-format "... %{+Q}hrl ..."
I'm not
Hi List,
We are experimenting here with the LDAP authentication provider against
the Windows Active Directory. All works fine!!
It is easy to ask for authorisation for a layer, and giving access via
'groups' instead of individual users is a nice thing.
BUT we also want to see in either Tomcat or
