Starting in 7.1.1, there can be no overlap in the root paths of access zones. The idea was that access zones should be separate zones that should not mix due to things like different authentication sources.
However, starting in 8.0, you can overlap the root paths again, but the GUI will warn you that you are doing it, but it will allow it. Between 7.1.1.x and 7.2.1.x, there is no exception to the rule.
Just be careful when doing so, especially with authentication.
One query here if root path for a zone is set to /ifs/customer what if we changes it to /ifs/customer/custA will there be any impact in accessing any shares or and communication failure with AD. I am asking this as its a production cluster and need to make changes.
AdamFox
254 Posts
0
February 9th, 2016 05:00
Starting in 7.1.1, there can be no overlap in the root paths of access zones. The idea was that access zones should be separate zones that should not mix due to things like different authentication sources.
However, starting in 8.0, you can overlap the root paths again, but the GUI will warn you that you are doing it, but it will allow it. Between 7.1.1.x and 7.2.1.x, there is no exception to the rule.
Just be careful when doing so, especially with authentication.
chughh27
39 Posts
0
February 11th, 2016 00:00
Thanks Adam,
One query here if root path for a zone is set to /ifs/customer what if we changes it to /ifs/customer/custA will there be any impact in accessing any shares or and communication failure with AD. I am asking this as its a production cluster and need to make changes.
Thanks
Chughh