return statement failure

[Alan DeKok]

On Sep 22, 2016, at 11:02 AM, John Kristoff <jtk at depaul.edu> wrote:
> Hah, apparently.  Legacy installs are confusing, especially when they
> did things they shouldn't have done.  There is another place in the
> config that has this and doesn't result in any noticeable errors:
> 
>  authorized {
>          eap {
>                  ok = return
>          }

  Read the documentation.  This is allowed for *modules*.

> *shrug*  Time to go through the config and validate everything else
> that might be a little wonky.

  Recent versions of 3.0 are much more picky about what they allow.  And, they complain in great detail, with very useful error messages.

  i.e. if it doesn't complain, it's likely fine.

  Alan DeKok.