On Sun, Jul 7, 2013 at 10:18 AM, Christian Mueller <
[email protected]> wrote:
> Hi Andrea
>
> 1) Our password encoders never produce the same result for identical plain
> text passwords. The encoding uses a random salt.
>
> 2) The post changed event is used by GeoServerSecurityFilterChainProxy to
> create the internal data structure for the filter chains.
>
> 3) What about checking the encrypted password
> with GeoServerPasswordEncoder.isResponsibleForEncoding(..). If the current
> config password encoder is responsible for the encrypted password, you can
> skip the recode logic.
>
Yes, this approach crossed my mind. However... is it possible to have a
configurable password encoder, that would take parameters to run, and thus
with the same encoder, the password structure would be different? I'm
probably just thinking too much...
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
