So this post last week got me a little nervous but I’d like to say a big thanks to @ABain for alerting us all. I think the ‘Release Notes’ updates recently have been a real step in the right direction.
I wanted to share my understanding of the issue to A. ensure I’m getting this right and B. allow others to more easily identify if their systems will be impacted or not.
My understanding is this issue will only impact users that are using the ‘AD’ idmap backend. As you can see in my case I’m using RID so this should not impact me. Users should be able to easily identify if their systems are going to be impacted simply by checking this parameter.
Currently you are unable to comment on ‘Release Notes’ posts so please free to comment here with any questions you may have and hopefully someone will have the answers for you.
There is no workaround for idmap_ad, we will have to release hotfixes for currently supported enterprise customers.
This comment in the original post seems to suggest iX are only going to roll out a fix to Enterprise customers however during this weeks T3 podcast that message seemed to suggest a fix would be available to all. Perhaps someone from iX can clarify this?