Hi Rodrigo.
First, you have to adapt ddl.xml AND dml.xml to get things working.
About password encoding. The idea is to give you the possibility to
implement your own password encoding. Your encoder must implement
org.geoserver.security.password.GeoServerPasswordEncoder
As an example for a digesting encoder, look at
org.geoserver.security.password.GeoServerDigestPasswordEncoder
Create your spring xml file and inject the encoder, sample in
applicationSecurityContext.xml
To see a text on the GUI, create a file GeoserverApplication.properties and
add line
myencoderspringbeanname= "Name I want to see at the GUI".
Hope that helps.
2012/6/1 Rodrigo Del C. Andrade <[email protected]>
> **
>
> Hello folks.
>
> Quick question, here is the setup:
>
> We are using 2.2 beta2 with the new security framework to integrate
> Geoserver and our users database, using the JDBC connector. The goal is to
> have Geoserver access our user info, wich is already in place.
>
> Initially I thought about "spring-extending" the sec-jdbc package so I
> could change how it access the databases, however, digging in the code it
> became clear that I can accomplish it by simply giving it my own ddl.xml
> (+10 cool points for that). But that still leaves me the problem of how the
> password is encrypted. The point is that Geoserver will have absolutely no
> write access to that database, as all the users are managed by our own
> application.
>
> However, in my tests the Geoserver encoded pass does not match the
> password created by our product (as was the expectation), so my guess is
> Geoserver wont be able to match what authentication pass the user provides
> with the one in the database. In our user management we use a digest
> SHA-512 to encrypt the users password.
> Now, I am having a spot of trouble locating where in the code the user
> supplied password is encrypted and matched against the one in the database.
>
> Could anyone point me at the right direction as to how to accomplish that
> and extend (doing a pluggable jar would be ideal) to provide another option
> on how the encryption is done, therefore adding to the Weak PBE, Strong
> PBE, etc, options of the security settings.
>
> Any info is hugely appreciated!
> Cheers!
>
> Rodrigo
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
