Sagewire Logo

Simple remote authentication

2 Message(s) by 2 Author(s) originally posted in java security


From: hacka Date:   Sunday, February 11, 2007
Hello,
I need to implement a simple login / password authentication for my
client -server application , preferably some kind of challenge-response
protocol. I'd like to use an existing solution (SASL + CRAM-MD5?),
but I am a bit overwhelmed by all the API's (SASL, JAAS etc.) and
really I need something simple. What'd you recommend?

Regards,
Mike.


From: Ralf Ullrich Date:   Sunday, February 11, 2007
wrote in message:

Hello,
I need to implement a simple login / password authentication for my
client-server application, preferably some kind of challenge-response
protocol. I'd like to use an existing solution (SASL + CRAM-MD5?),
but I am a bit overwhelmed by all the API's (SASL, JAAS etc.) and
really I need something simple. What'd you recommend?
Regards,
Mike.



Using SASL is actually quite simple and straightforward. You've to
create a SaslClient (sc) on your client side, and a SaslServer (ss) on
your server side. Then on both sides you've to write a loop that is
controlled by the sc/ss object. During this loop the callback handler,
that you provided when creating the Sasl* objects will receive callbacks.
After the loop finishes, you'll know wether the authentication was
successful or not.

All you need to know to successfully use SASL is described here:

JAVA SASL Programming Guide -
http://JAVA.sun.com/JAVAse/6/docs/technotes/guides/security/sasl/sasl-refguide.html

Ah, and one thing I should mention: you've to define the messages in
your application protocol, that will encapsulate the SASL-messages to be
exchanged. This is only indicated in the above guide through "send(...)"
and "msg.receive()" calls. If you need an idea how to do this, look into
the RFCs regarding the use of SASL in SMTP or NNTP (Sorry too lazy to look
'em up for you). However it's quite easy, just define messages, that can
transport some binary data (the SASL data), and have an associated status
of Continue, Success or Error. (Just look at the "send(...)" calls in the
guide, and you will know what types of messages you need.

cu



Next Message: Need help of providers for RC2 encrypt/decrypt


Blogs related to Simple remote authentication

java faqs
EEJB was originally designed around remote invocation using the Java Remote Method Invocation (RMI) mechanism, and later extended to support to standard CORBA transport for these calls using RMI/IIOP. This design allowed for maximum ...

Web-Centric Production Acceptance
Designing and implementing methods for remote user authentication and data encryption. Network Engineering Typical responsibilities of Network Engineering include:. Determining internal networking requirements, both for WAN's and LAN?s ...

Wicket Impressions, moving from Spring MVC / WebFlow
The old application was using the Acegi security framework. I started out retaining Acegi for authentication and co-existing with Wicket, which was easy. I soon realized that Wicket has a very simple authorization strategy and I was ...

Server 6.5 SP6 Abend
NLM Simple Authentication and Security Layer 3.1.2.0 20061014 Version 31200610.14 14 October 2006 Code Address: 951F3000h Length: 0000140Ch Data Address: 9557F000h Length: 00000090h LSL.MPM lsl Memory Protection Module ...

Flex Data Services and Tomcat Authentication - Part 2: Simple ...
In the dialog, look for the Configuration titled “Remote Java Application. Select it and click on the ‘New’ button. Select the Project to “flex-auth-webapp”, select the Connection Type to “Standard (Socket Attach)”. ...

How to implement your own Security provider with the Acegi framework.
Using eclipse we can configure a remote debug application:. The implementation of the Authentication interface used by Acegi is an instance of UsernamePasswordAuthenticationToken as we can see when debugging the application. ...


Programming | Sports | Autos

copyright 2006
Valid XHTML 1.0 Transitional