From: Miroslav Nachev <miro_at_space-comm.com>
Date: Tue, 15 May 2007 18:46:25 +0300

I would like to repeat the same logic like Web browser because there are too many applications working with this logic. Of course the Swing client will work directly with EJB3 instead with Web tier. I would like to do that because the bank branch use this and they believe (trust) to this technology. Also this technology is good and it is not necessary to create new one just to be different from Web technology. Why to do something new in case that we can use the idea which is good and to implement to Swing?

if it is the case that you want the client to send a cryptographic authenticator in the request message, can you provide a little more detail as to the form of the authenticator? will it be added as  added as a header that will be available to the server via the HttpServletRequest api, and if so, what will be its format.

I am not familiar with the exact technology because the used one in Bulgaria is Microsoft based, but I am familiar with Java Security, Java XML Security and other security standards like XAdES, so I can use this. Also, the technology is common I think because this works with MS Internet Explorer and Mozilla Firefox with the same way. After the Username/Password pass successfully, a new message box (Dialog) is shown where I am prompted to enter the PIN code for the SmartCard. Then if on the SmartCard are located more than one certificates I have new Dialog where are listed just these certificates which are for the current bank. I choose the right one and then the Certificate authorization pass successfully. Please find the attached snapshots:
1. Login-stage-1-username-password.jpg
2. Login-stage-2-certificate-selection.jpg
3. Login-stage-3-certificate-authorization.jpg
Please note, that the request which is coming from the Server is related with the used username. That's why I have to choose this Certificate Principal which correspond to the login username.

If you can show me a sequence diagram of the authentication dialog, I shoulkd be able to map your protocol onto a ServerAuthModule.
Can you provide a reference to the "banking authorization process" you are using?

No	Client	Direction	Server
1	Create SSL	=>
2		<=	Request for Username/Password
3	Answer: Send Username and Password	=>
4		<=	If success, send request for the Certificate  Authorization using Subject/Issuer (X509Principal) and other (I don't know what exactly if any)
5	Looking for Certificate stores (PKCS#11, PKCS#12, JKS, etc.)
6	If there are more than one certificates with this issuer (bank) then show the Dialog for choice (we can use Subject instead Issuer and in this case we will know exactly which is the needed certificate)
7	The Client is asking for the password (PIN) of the Certificate Store
8	Some MD/Sign is calculated using the Private key
9	The MD/Sign is send to the Server	=>
10			The Server check this MD/Sign using Public key.

Regards,
Miro.


Ron Monzillo wrote:

Miroslav Nachev wrote:

Dear Ron,

I mean this:

a. the user agent (which appears to be a browser) is using the private key corresponding to its certificate to produce a crytographic authenticator for verification by the server, or

In my case I would like the web browser user agent to be replaced from Swing user agent. I think that this will not be a problem. The certificate with related private and public keys are on the client side. The server side keep only the certificate and public key.

Miroslav,

it sounds like, swing user agent will exchange a username and passord over ssl, and then it will use a private key to sign something which will be sent to the server (over the ssl protected transport), and the server will use the corresponding public key to validate that the corresponding privaye key was known to the user agent.

I can accept that a swing user agent could do the above, but this seems like more than could be expected from a typical browser, and it sounds like you are trying to write a swing client that does what would otherwise be done by a browser, and that you want to be able to extend the server side to support such clients.

if it is the case that you want the client to send a cryptographic authenticator in the request message, can you provide a little more detail as to the form of the authenticator? will it be added as  added as a header that will be available to the server via the HttpServletRequest api, and if so, what will be its format.

I still am not sure I completely understand your client and the type of messages that it will send, but i think you will be able to perform the server-side processing by writing a ServerAuthModule as described in chapter 3 of the jsr 196 specification.

If you can show me a sequence diagram of the authentication dialog, I shoulkd be able to map your protocol onto a ServerAuthModule.

Can you provide a reference to the "banking authorization process" you are using?

Ron

Best Regards,
Miroslav Nachev


Ron Monzillo wrote:

Miroslav Nachev wrote:

Hi Ron,

I don't fully understand your use model (especially the relationship between 4.3 and the username/password mechanism

In Bulgaria and in tested European Internet banking the authorization process is in 2 stages:
1. SSL Username/Password

Miroslav,

I still don't understand.

I presume step 1 is BASIC Auth over SSL or (something equivalent).

2. Certificate authorization where the certificate is generated from the bank in most cases.

what exactly is step 2. For me to understand, it would help to show the msg flows, but maybe you can just answer the follwoing.

By "certificatate authorization" do you mean

a. the user agent (which appears to be a browser) is using the private key corresponding to its certificate to produce a crytographic authenticator for verification by the server, or

b. the user-agent/browser is verifying the certificate of the server, to ensure that the browser is communicating (i.e. exchanging its password) with the proper service, or

c. something else

thanks,

Ron

ps: in jsse, (b) can be implemented using a hostname verifier; but in this case, the verifier runs just after the ssl handshake is complete, and before the username and password is exchanged.

If the Username/Password is not passed, then the 2nd authorization (certificate) is not started.
If the Username/Password is passed, then the certificate authorization is started. If and only the certificate authorization is passed you can continue with Internet Banking. At the moment Web certificate authorization use the default certificate store in the active web browser like Mozilla or Internet explorer. In my case I use PKCS#11 (SmartCard) to store the certificates. Before I am used PKCS#12 or integrated.


Regards,
Miro.


Ron Monzillo wrote:

Miroslav,

I don't fully understand your use model (especially the relationship between 4.3 and the username/password mechanism, but that may be immaterial. Let me try to focus on your first question. Glassfish is the reference implementation for jsr 196, which is the java authentication spi for containers. The spec is in proposed final draft, and will soon be submitted for finalization ballot.

Chapter 3 of the spec defines how to use the spi to add support for a new authentication mechanism to a compatible servlet container.

The spec does not define interfaces for items 5 and 6 in your list; however, it may be best to handle both by directing the user to interact with an authentication service on which the application/servlet container relies (such as an openSSO identity provider).

The 196 spec can be found at:

http://jcp.org/en/jsr/detail?id=196

Ron

Miroslav Nachev wrote:

Hi,

I am going to design and develop new SwingX based Login dialog (see the attached images), because the existing one which is in the GlassFish is not enough. I am not sure but I think that the new functionality will require new Server part.
*Can you give me some suggestions how to do the server part?*

The functionality is as follow:
1. Username/Password login;
2. After unsuccessful authorization the Error message dialog will be shown (wrong username or password).
3. After Cancel or Close nothing will happen
4. After successful authorization:
    4.1. the username and language will be saved in the user local profile to be used on the next login in ComboBox;
    4.2. if remember password is checked the password will be stored in the user local folder in JKS format;
    4.3. if on the Server part is checked Certificate authorization which is required for the Bank authentications the Certificate authentication will be started.
5. If the user is new, then can be used button for new user registration in "Options" expansion.
6. If the user can not remember the password, the "forgot your password" can be used from "Options" expansion.


Best Regards,
Miroslav Nachev

------------------------------------------------------------------------


------------------------------------------------------------------------


------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: dev-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: dev-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: dev-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net