This would be a possible way. Now the question is which algorithm
implementation of md5 PostgreSQL uses... Bye, Thorsten Ben Trewern schrieb: You could originally connect to the database as some kind of power user. Check the password against the pg_shadow view (you would need to md5 your password somehow) and then do a SET SESSION AUTHORIZATION (or SET ROLE) to change your permissions. Not sure how secure this would be but it's the way I would try. Regards, Ben "Thorsten Kraus" <TK-Spam@xxxxxx> wrote in message news:46124F74.3000302@xxxxxx...Hi, thanks for your answer. I cant use the username/password in my DSN because I don't connect directly via JDBC to the database. I use hibernate for all database actions. The username and password has to be stored in the hibernate configuration file... Bye, Thorsten Lutz Broedel schrieb:Can you not use the username/password as part of the DSN? Regards, Lutz Broedel---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |