James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
Originally posted by James Turner:
It would use LDAP to compare the username and passwords.
Originally posted by James Turner:
I surpose the login module would sit on the client.
Originally posted by James Turner:
Can the login module sit on the server?
Originally posted by James Turner:
Is there a way for a swing client to login remotely?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by James Turner:
... what is the best way for a Swing client to communicate with the server side application?
...
2. Web Service calls via the web container.
Originally posted by James Turner:
I think that for the purposes of our application, direct communication with the EJB's is better because all agents will be within the companies firewall and will have no difficulty talking directly to the EJB.
Originally posted by James Turner:
I think that web [interfaces] are good for Swing clients that are external to the companies intranet, i.e. outside the firewall.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by James Turner:
are you saying that web services are the way to go for connecting a swing client to the EJBs?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
Originally posted by James Turner:
I am sorry I am a little lost here...
Originally posted by James Turner:
I should then communicate with the EJB's directly via RMI/IIOP?
Originally posted by James Turner:
how do I authenticate the Swing client so that it can pass the security context so it can access the secured EJBs?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Johnty Rhodes:
I think in Weblogic (weblogic.jar) Authenticate.authenticate() does this.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
James<br />SCJP 1.4 - 92%<br />SCJD - 93%<br />SCWCD 1.4 - 95%<br />SCBCD 1.3 - 100%<br />SCEA - 92%
If at all possible I would like to follow the standards route;
Originally posted by James Turner:
If at all possible I would like to follow the standards route
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Thomas Taeger:
2. What in general are the advantages of JAAS compared to standard form login?
I feel that you assume that only JAAS were a standard.
1. What are the reasons why JAAS necesseraly must be used?
I surpose the login module would sit on the client. It would use LDAP to compare the username and passwords.
Originally posted by Maris Orbidans:
We are discussing authentication of SWING clients.
Originally posted by Maris Orbidans:
Of course, in practice we often use vendor specific JNDI authentication, but it's not ideal.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
To be honest, the term "JNDI authentication" (or "vendor specific JNDI authentication") is new to me.
What I know is authentication via LDAP and accessing the LDAP server through JNDI as usual. Is this what you mean?
That is why I would like to hear some reasons why it is worth for me to learn more about JAAS.
Especially what are the reasons why or when JAAS necesseraly must be used?
Why do you think authentication through LDAP (via JNDI) is not ideal? What are the reasons?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
JAAS Login Modules
VBCS uses the Java Authentication and Authorization Service (JAAS) framework provided by Sun Microsystems to offer authentication hooks, specifically through JAAS Login Modules.
The JAAS framework supports multiple Login Modules, which can be used in conjunction with one another. Each Login Module defines one type of authentication.
For example, an installation that has an HTTP basic Login Module may or may not include a Login Module that performs an LDAP lookup or bind. Use of multiple Login Modules is known as stacking.
The JAAS configuration can specify that both modules must return a login success before user authentication is approved, or that the basic module is sufficient for authentication and that the LDAP module is used if the first module fails.
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.