RE: How to handle non digest messeg if Auth-Type is set to Digest?

2006-07-28 Thread GlobeInPhotos
No. It is IMPOSSIBLE for Auth-Type to be in a RADIUS packet. I've commented line in users file #DEFAULT Auth-Type := Digest But now I've got following message if non-digest message arrive: rad_recv: Access-Request packet from host 153.19.130.250:46963, id=190, length=80 User-Name =

How to handle non digest messeg if Auth-Type is set to Digest?

2006-07-27 Thread GlobeInPhotos
Hi My Freeradius has to receive and process digest and non-digest message but when freeradius receives and process nondigest message (I have only one such message) I've got message: ERROR: You set 'Auth-Type = Digest' for a request that did not contain any digest attributes!

RE: How to handle non digest messeg if Auth-Type is set to Digest?

2006-07-27 Thread GlobeInPhotos
So the conclusion is that you set Auth-Type = Digest somewhere. Probably OpenSer which is a sender set Auth-Type=Digest in request. By the way is it possible to make workaround for such situation to be honest I do not need authorize message but only I have to send some values to OpenSer -

RE: How to handle non digest messeg if Auth-Type is set to Digest?

2006-07-27 Thread GlobeInPhotos
Go back and read the debug log. Check your configuration. YOU set Auth-Type in YOUR configuration. Are you talking about radius config? In my config I have something like this. authorize { cut Digest cut } I can send Stop arguing, and go check it. For sure I'm not arguing but

RE: How to handle non digest messeg if Auth-Type is set to Digest?

2006-07-27 Thread GlobeInPhotos
-Type is set to Digest? GlobeInPhotos [EMAIL PROTECTED] wrote: So the conclusion is that you set Auth-Type = Digest somewhere. Probably OpenSer which is a sender set Auth-Type=Digest in request. No. It is IMPOSSIBLE for Auth-Type to be in a RADIUS packet. Go back and read the debug log