Currently, we have a very stable environment in Production - version
SDL Tridion 2013 SP1 HR1 with a fully-functioning nested (most complex permutation is 3 groups deep) security model.
For example, Advanced Producer is a member of Producer group and Producer is member of Read-Only group.
So there is a base Read-Only group; then another slightly more capable Producer group with
W/R capabilities; then more advanced Producer group with
W/R/L/D; and finally a group with only
Translation Management enabled that each user is apart of explicitly, which is inherited only from Read-Only group.
So when I upgraded to SDL Web 8.1.1 release in a lower environment that has been previously restored from Production; and there have been no changes to the Production groups since restore..
When I go in as a Producer or Advanced Producer in newly upgraded 8.1.1 instance to smoke test/regression check our products, the existing security model - as it works today in Production, does not work as expected. Immediate differences would include opening a component and not having permission to read/view fields that is local to that publication or when trying to edit from Parent. We did our due diligence and compared permissions from upgraded instance vs. Production and indeed, they are identical.
Oracle Database Information
- 64-bit ODAC 12c Release 1 (22.214.171.124.0) for Windows x64 [Released August 13, 2013]
Has there been any Security Model changes we need to be aware of with 8.1.1 upgrade/release? If indeed, this is a permission issue.. which seems to be the ghost I am chasing thus far.