[Geoserver-users] GeoServer 2.6.1 JDBC Authentication

GeoServer GeoServer User
1

Hi All,

I noticed that after upgrading from 2.5.2 to 2.6.1 that my JDBC authentication doesn’t work anymore. This is how I made my JDBC authentication provider. I first make a new JDBC user group service and then I make a new authentication provider using that service. This was fine for 2.5.2, but in 2.6.1 none of the users I created with the JDBC service worked. What’s weird is that if I used my database connection username and password, GeoServer accepted that.

Is anyone else having problems with JDBC authentication in 2.6.1?

Thanks,
Danny

2

Hi Danny,

···

2014-12-10 1:23 GMT+01:00 Danny Cheng <dcheng@anonymised.com>:

Hi All,

I noticed that after upgrading from 2.5.2 to 2.6.1 that my JDBC authentication doesn’t work anymore. This is how I made my JDBC authentication provider. I first make a new JDBC user group service and then I make a new authentication provider using that service.

What kind of authentication provider is using the JDBC usergroup service?

This was fine for 2.5.2, but in 2.6.1 none of the users I created with the JDBC service worked. What’s weird is that if I used my database connection username and password, GeoServer accepted that.

Probably something is different in your authentication configuration from 2.5.2 to 2.6.1.
The behaviour you are describing is not an issue, is the way the JDBC Authentication Provider is meant to work: the JDBC Authentication Provider authenticates you using the database username and password, while the JDBC UserGroup Services stores users/groups information on database tables, but needs to be bound to an AuthenticationProvider such as the UserNamePassword one.

Mauro

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Please, notice that GeoSolutions will be closed for seasonal holidays
from December the 24th to January the 6th

Dott. Mauro Bartolomeoli
@mauro_bart
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

3

Hi Mauro,

Your second point was my problem. I was trying to bound my JDBC usergroup service to JDBC provider and not UserNamePassword one. My bad.

Thanks,
Danny

···

Hi Danny,

2014-12-10 1:23 GMT+01:00 Danny Cheng <dcheng@…3836…>:

Hi All,

I noticed that after upgrading from 2.5.2 to 2.6.1 that my JDBC authentication doesn’t work anymore. This is how I made my JDBC authentication provider. I first make a new JDBC user group service and then I make a new authentication provider using that service.

What kind of authentication provider is using the JDBC usergroup service?

This was fine for 2.5.2, but in 2.6.1 none of the users I created with the JDBC service worked. What’s weird is that if I used my database connection username and password, GeoServer accepted that.

Probably something is different in your authentication configuration from 2.5.2 to 2.6.1.

The behaviour you are describing is not an issue, is the way the JDBC Authentication Provider is meant to work: the JDBC Authentication Provider authenticates you using the database username and password, while the JDBC UserGroup Services stores users/groups information on database tables, but needs to be bound to an AuthenticationProvider such as the UserNamePassword one.

Mauro

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Please, notice that GeoSolutions will be closed for seasonal holidays
from December the 24th to January the 6th

Dott. Mauro Bartolomeoli

@mauro_bart

Senior Software Engineer

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.