Sharing a radius authentication-profile from panorama to a vsys-enabled firewall ?

[Bart_Jocque]

Hi,

When I define a shared radius-authentication-profile on panorama , this profile gets published into all my panorama managed firewall.

So far so good.

But when this gets pushed to a vsys-enabled firewall, then the authentication profile is pushed only into the vsys-contexts and not into the device context.

-> This has as result that the radius authentication profile in question can not be used as device authentication-profile for non-local administators on that firewall. It is simply not visible in the device-context, so it can not be selected.

Is this a bug are normal behaviour  ?

btw , we are on 4.0.3.

[mschuricht · Accepted solution]

Unfortunately, this is not a bug and happens to be a limitation of the current Panorama design. You are absolutely correct about the objects being pushed into vsys-contexts and not the "shared" device context. This is where the auth profile needs to be for selection inside Device > Setup for enabling RADIUS auth.

For now you will need to create the profile on each box where you wish to use this authentication mechanism.

We are looking at enchancing the Panorama architecture to support pushing objects to non-vsys contexts in a future release.

Sorry for the inconvienence.