hi

has anyone else observed, that the defined skin for the coresponding user group is not applied when the user gets authenticated via AAA?
this furthermore only affects winbox skin. if the AAA user logs in via WebGUI it works properly.

if a local defined user is logging in, the skin gets applied correctly
the modified skin is the "default" skin, which is applied to all user groups

left winbox window is logged in with a radius AAA authenticated user, which gets the group "full" applied - skin in winbox not applied (webGui = OK)
right winbox window is logged in with a local user on that CCR. "default" skin is applied correctly.

anyone?

Not directly related to you specific issue, but today I found out:

Created a user with group-policies=read,winbox,webfig,ssh. Skin applies perfectly on webfig, but Winbox ignores the skin. Already filed a support ticket for that.

WinBox is a b*tch. Hopefully the "new winbox" does it better overall.

Not directly related to you specific issue, but today I found out:

Created a user with group-policies=read,winbox,webfig,ssh. Skin applies perfectly on webfig, but Winbox ignores the skin. Already filed a support ticket for that.

WinBox is a b*tch. Hopefully the "new winbox" does it better overall.

winbox only respects/"reads" the "default" skin. so when you change the skin "default", winbox applies that skin. but only on local users (not, as mentioned, for RADIUS/AAA authenticated users - which do get applied the same group via AAA like a local "full" user)

MT support confirmed: it is a WinBox bug in my case. The user needs policy "sensitive" as a workaround.