Upgrading to a newer version fixed this for us. We were on 2.1.2 and now are on 2.1.5. I think this issue was reported and fixed in 2.1.3.
-- Sent from: http://syncope-user.1051894.n5.nabble.com/
Upgrading to a newer version fixed this for us. We were on 2.1.2 and now are on 2.1.5. I think this issue was reported and fixed in 2.1.3.
-- Sent from: http://syncope-user.1051894.n5.nabble.com/