Environment
Novell Access Management
Novell Access Manager 3 SP1 Beta 1
Novell Access Management 3 Linux Access Gateway
Situation
When Lag settings are modified on a beta 1 SP1 system and an
authorization policy applies to certain users they loose there role
information resulting
in a random 403 (so not all users) for already authenticated and authorized users.
For those users, they had to re-login so that the role/authorization policies would work properly.
in a random 403 (so not all users) for already authenticated and authorized users.
For those users, they had to re-login so that the role/authorization policies would work properly.
Resolution
This has been fixed with latest builds shipping with Novell Access
Manager 3 SP1 Release Candidate 1 or later.
Additional Information
Steps to reproduce:
Make an accelerator on the LAG and have a role based authorization policy assigned to the accelerator.
Log in from different browsers with a couple of users that fall under the authorization policy.
Add an additional DNS server or make another change to the LAG which requires the "All Configuration" type of change.
Apply the change and do the update for the "All Configuration"
Refresh browsers for the authenticated and authorized users and you will get the 403 on a couple of them.
It seems to be random so not always it fails for all users.
Make an accelerator on the LAG and have a role based authorization policy assigned to the accelerator.
Log in from different browsers with a couple of users that fall under the authorization policy.
Add an additional DNS server or make another change to the LAG which requires the "All Configuration" type of change.
Apply the change and do the update for the "All Configuration"
Refresh browsers for the authenticated and authorized users and you will get the 403 on a couple of them.
It seems to be random so not always it fails for all users.