Did another downgrade to 4.6 this time and here the issue seem to be gone.. I can reload/restart and the commands gets authorized as they should..
Another issue that seem to be gone with 4.6 is that the first request to a Radiator 4.9 tacacs server fail, second and onwards works as they should. Regards, Patrik Forsberg -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Patrik Forsberg Sent: den 16 april 2012 12:57 To: Heikki Vatiainen; [email protected] Subject: Re: [RADIATOR] Tacacs Authentication to survive reloads ? To follow this up .. I tried downgrading to 4.7, with patches, and it seem to have the exact same issue.. Regards, Patrik Forsberg > -----Original Message----- > From: [email protected] [mailto:radiator- > [email protected]] On Behalf Of Patrik Forsberg > Sent: Friday, April 13, 2012 3:52 PM > To: Heikki Vatiainen; [email protected] > Subject: Re: [RADIATOR] Tacacs Authentication to survive reloads ? > > > The patterns received with AuthorizeGroupAttr are stored in the context > > and override the patterns in the config file. Now when the context is > > gone with the reload, the possible overrides are gone too. I think this > > is the reason why it refuses to process authorization. The authorization > > patters may no longer be correct without the overrides. > > So.. downgrade to pre-4.8 ? > or any way to re-instate the context(s) after a reload in some way ? > or is there something in the configuration I can change to make it "better" > for > the tacacs server ? > > Regards, > Patrik Forsberg > > _______________________________________________ > radiator mailing list > [email protected] > http://www.open.com.au/mailman/listinfo/radiator _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
