Hi Kris,
As mentioned above, I'm by no means familiar with the authentication options
for GeoServer, so I'll do my best to help with debugging it yourself.
You say you use a Docker container. Did you look at the installation script?
Try and remove any line that pulls in and installs the authKey m
Hi Manuel,
I tried rebuilding my geoserver (I run it as a docker container), which has
fixed some issues in the past, but did not work this time.
I think the issue may be that I need to disable authKey authentication but
to do so I need to access the Authentication page. But when I attempt to
acce
Hi Manuel,
I think you might be on to something with the authKey exception. I did
experiment with using authKey, but forgot about it and maybe changed a
setting that is throwing off the whole site. I'll look into that.
On Sat, Mar 31, 2018 at 10:42 AM, timita wrote:
> Hi Kris,
>
> The way I wor
Hi Kris,
The way I work with GeoServer is to write comprehensive Node.js wrapper apps
around it, with their own authentication mechanisms and the rest, and only
control it via REST. So I'm not familiar too much with GS's auth system. I'm
trying here my best, mostly guiding you with respect to debu
Hi Kris,
One ca see a 'Bad credentials' exception in your logs, but it is difficult
to say whether that is exactly the cause, or something else, give the noise
in the file you attached.
I would recommend to clear the log, set it for 'PRODUCTION_LOGGING' (see
here how:
http://docs.geoserver.org/la
