In ours, we now use an Java Applet client (embedded in dumb HTML pages) and an architecture with Java Server Communication by sockets (on SSL).
Users will have to enter the system using the username and password (hopefully not shared) - then the password is stored in the hashed form in our database.
After reading Jeff recently, I think our users have to think about allowing login with alternative mechanisms such as OpenID, so remember them the username and password Not necessarily, but we still know that the user is the same day that was logged a day ago from any other computer.
As far as I understand, OpenID works by using browser redirects in conjunction with some server-side cryptography, it combines our applet (or applets with a non-HTTP server combined) To feel complicated (if not impossible), that should allow entry here.
OAuth either uses the same mechanism, or a token given to some user, which user will then input into my applet. The applet will have to store this token on the client (per JNLP persistence service or similar) to allow for repeated admission, but this would mean that every computer has to get a new token, easily access to many user computers (accounts) Do not share, and too much login is not easy.
Are there any other methods here that can be used to enable a single sign-on system, or it is simply impossible without at least some HTTP-server side code transfer Credential to our applet?
To log in to your users, use OpenId to log out of the applet One of the can This will be the normal flow, which will include server-side processes and user redirects on the page of the OpenID provider. You then pass the User ID in the applet:
& lt; Object codetype = "application / java" ... & gt; & Lt; Param name = "user" value = "myOpenId" & gt; & Lt; / Object & gt; Then you this.getParameter ("user") . can authenticate a user.
Comments
Post a Comment