You need to look in the GeoServer log file to find out what's gone wrong.
You really need to add some more detail as to how you put the roles into
PostGresql
Ian
On Tue, 9 Mar 2021 at 05:52, krishna lodha wrote:
> Hi, I tested the solution https://gis.stackexchange.com/a/388940/79 mentioned
>
Hi, I tested the solution https://gis.stackexchange.com/a/388940/79 mentioned
here, it works perfectly fine as long as roles are Default when I tried to
put roles in PG as well, it gives me HTTP error 500 for the users.
What should I do?
[image: Screenshot 2021-03-09 at 11.20.20 AM.png]
On Sat,
Absolutely. We use PG to control authentication across our entire system.
This includes authenticated WMS calls to geoServer. It's critical for us.
On Wed., Mar. 3, 2021, 11:01 a.m. Andrea Aime,
wrote:
> Each of those source file has an author tag, they all say:
>
> @author christian
>
> About
Each of those source file has an author tag, they all say:
@author christian
About a reason to do so, database centric security can be a reason. A
system where the access restrictions are enforced
at the relational database level. In that case, you want to authenticate
using database users, and
So who did write it? I'm still trying to come up with a reason to let my
database users log into geoserver.
Ian
On Wed, 3 Mar 2021, 17:39 Andrea Aime, wrote:
> Quoting from stack overflow: "After much head scratching and asking the
> guys who wrote this stuff on the users mailing list"
>
>
Quoting from stack overflow: "After much head scratching and asking the
guys who wrote this stuff on the users mailing list"
Hell no, I had nothing to do with those modules! :-D
Cheers
Andrea
On Wed, Mar 3, 2021 at 6:35 PM Ian Turton wrote:
> Thanks to everyone for their help on this I have
Thanks to everyone for their help on this I have finally got my head around
it and have added an answer to the gis.stackoverflow question I linked to
earlier (https://gis.stackexchange.com/a/388940/79) - If I get some time
over the weekend I'll see if I can try to make the documentation clearer.
Hi Ian,
the role handling is a third class:
[image: image.png]
1: authentication via database users (tries to connect to the database
using the username/password provided in the request)
2: authentication via table contents (looks up a user with the same name
provided in the request, and
On Wed, 3 Mar 2021 at 13:33, Andrea Aime
wrote:
> Hi Ian,
> there are both functionalities, they are separate classes and are
> configured in a different way:
>
>
>- Authenticating using the database own users:
>
>
Hi,
So the bottom line is we can’t use database to store users? That can be
then used further to login to geoserver ?
On Wed, 3 Mar 2021 at 19:23, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> Hi Ian,
> the JDBC Authentication Provider is meant to be used to login using the
Hi Ian,
the JDBC Authentication Provider is meant to be used to login using the
database (e.g. postgresql) users.
If you want to store your own users on a database, the JDBC UserGroup
Service has to be used (together with the standard UsernamePassword
Authentication Provider).
I know it's
Hi Ian,
there are both functionalities, they are separate classes and are
configured in a different way:
- Authenticating using the database own users:
https://docs.geoserver.geo-solutions.it/edu/en/security/jdbc_authentication.html
- Storing credentials in the database, use the table
Hi Ian,
Thanks for getting back, the stack exchange denotes the exact problem I’m
facing. The new “users” are created but they can not be used to login, only the
‘users’ which are user of PostgreSQL can be used to login
Thank you,
Krishna G. Lodha
On 3 Mar 2021, 5:04 PM +0530, Ian Turton ,
Just to check before I break out the debugger:
When you use JDBC Authentication can it allow any user you create in
GeoServer (which get written in then tables) login in or does it only
allow the user used for the postgis connection (or other postgis users) to
log in?
It seems like this is a
14 matches
Mail list logo