Re: [Beepcore-java-users] Requireing a profile

[William J. M. <wm...@ol...>]

I think this is a case where the profiles need to do the right thing, rather than
the core functionality.  I may be wrong.  

SASL sets a state in the session, but to some extent it is the profiles which
must honor this.  Tuning profiles which casue a new greeting to be exchanged
give the opportunity to register new profiles, and advertise them at that time,
which would do what you want, but SASL/ANONYMOUS does not cause a tuning reset 
in this way (as far as I know).

So for the ECHO example, you'd need a custom version that checks authentication 
in it's start message handler.

Someone please correct me if I am mistaken.

-bill

On Sun, Aug 04, 2002 at 05:20:46PM -0700, Kevin Kress wrote:
> In the SASL profile (or possibly a TLS) what is the mechanism used to
> send out "530" errors if the server wants to require authentication. 
> 
> For example, when a server starts up, it registers both, SASL/ANONYMOUS
> and ECHO... the desired result being that until the SASL/ANONYMOUS has
> set credentials in the Session, all other startChannel messages (in this
> case ECHO) will return with a <error code='530'> . 
> 
> If this is not done yet, where might it fit best?  A function of Session
> for the error sending?  Possibly ProfileRegistry for initial setup or
> TCPSessionCreator to setup the required auth?
> 
> thoughts? 
> 
> --Kevin Kress 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Beepcore-java-users mailing list
> Bee...@li...
> https://lists.sourceforge.net/lists/listinfo/beepcore-java-users