-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stéphanie,
It sounds to me like you're not sure what you want. Your original message was asking about how to authentication against a local Microsoft Windows user database (that is, NOT ActiveDirectory, which should be trivial). Now it sounds like you want to enforce all kinds of constraints on passwords, etc. Let's solve one problem at a time. On 3/31/2010 11:25 AM, Stéphanie Cettou wrote: > I have a JSP application and tomcat 5.5. > > my goal it to implement a login for this application with this mandatory > rules: You can deal with password complexity once you've decided how your passwords will be stored and how they will be set. For example, typically when authenticating against ActiveDirectory, the webapp itself does not provide a way to change an AD password. When passwords are set is the appropriate time to check for required complexity. Password expiration should also be done by some other means: Authentication just checks credentials. > The user must can connect from more pc, the finally application is in > a Windows 2003 server. So, you have the webapp running in a Microsoft Windows 2003 Server environment: good to know. Is ActiveDirectory being used in this environment? If so, use it. If not, don't set up AD just for your webapp. > I don't know if I can use active directory (create a new active > directory only for this application = install a new server), or others > things... > I don't know if I need to implement this in java, or a existing > solution is ready... An existing solution is probably already available... in Java. > I don't have a lot of knowledge in active directory, tomcat, NTLM or > Kerberos, .... If you don't know what you're doing, I highly recommend that you find someone who does and make this their job to do. > I need to be sure to choise the good solution for all point of my goal > while I can't spent a lot of time, and I can't change my solution > later... Do you have a user database against which you'd like to authenticate users? If that database is separate from Microsoft Windows (say, a RDBMS), then you don't have to mess with AD/NTLM/whatever: just use one of the standard Tomcat realms to do authentication for you. If you *must* use the Microsoft Windows user database, then you should look for a Java product that can authenticate against such a database. So, which is it: a) Do you have AD already? b) Do you have to authenticate against local Microsoft Windows User DB? c) Can you use your own database? I'm still not really clear on what your situation is. > can you give me more informations, please? I don't have enough > knowledge to choise the the simplest and best solution now... You are asking about implementing user authentication, which is typically an integral part of your security policy. If you don't understand what you are doing, anyone could give you horrible advice. My advice is to make sure you understand what you're doing before you do it. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuzkiEACgkQ9CaO5/Lv0PCU3ACfd2wX88utKny/EEDEFxROcFl+ W6gAnAktwUL/CWvTW8C3+4jocKqCnl5d =fRvV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
