I know this is probably a Java question rather than JSF, but I suspect someone here has probably ran into this before.
I have an application that requires me to grab the user's login information -
in particular their login name, and check that against a database.
I then need to do some verificaion or require the user to create a new account.
How do I access the user's login information?
With Studio Creator:
- Create a page "Login" (Creator creates a JSP ("Login.jsp") and a page bean which is a java source file "Login.java").
- In design view drop a Text Field, a Password Field and a Button from the palette on the page.
- Doubleclick the button. (Creator creates an action method in the page bean.)
- Write
String username = (String) this.textField1.getText();
String password = (String) this.passwordField1.getText();
(You can use a binding too instead of manipulating the component instances directly.)
- Set a breakpoint to the first line.
- Press F5 or choose Run - Debug Main Project.
In doing a bit of searching, I ran into System.getProperties() that seems to be able to get things like user.name.
Not sure if this will get the user name of the person accessing from a client side or if it is the username of the owner of the application on the server.
Can anyone shed light on this?
Also, what needs to be set in the 'server.policy' file?
I granted 'AllPermission' in order to do some testing, but I know there has to be a more limited permission that will do the job. I just don't kow what it is.
Basically, this is how it needs to work.
The application will be on a server on our corporate network.
Users login to the network with their usernames and passwords.
When the user brings this web application up in their browsers, I need
to be able to identify the username of the user.
I then need to check the database to see if that user has registered for the application.
If not, then I present the user with a screen to create an account associated with the application.
If the user is registed, then he can login into the application.
Form based: let the user register and choose an username/password to login with. Just create some simple forms and eventually add a Filter.
HTTP based: generally you define usernames/passwords yourself. The user will retrieve a browser default login popup when he access the restricted pages.
Another solution to crawl in the clients system is to use a signed applet instead of a webapp.
I recommend just form based authentication though. Less effort after all.
