First and foremost, if you're a commercial customer, you are entitled to Standard or Premium support based on your contract status. If this is a critical system, please use the "contact us" link to work with Tech support. In addition, you should have a portal account, your sales counterparts will be happy to set this up.
I had a chance to take a look at your log files. In summary, like you stated in the original post, there's nothing wrong with the user account
However, there are certain things wrong with the configuration that may or may not be contributing to the user's issue. This system is running in Express mode and is using features (passwd/group overrides, groups.allow, etc) that were sunset from the freemium version 2 years ago due to abuse (see reference below).
If you are a commercial customer, you should be using your standard edition to truly enforce access control and use UNIX identity management with AD.
If you are intending to run these in Express mode, clean the .ovr .allow files and perform an adreload. Express is for AD integration and authentication; you can implement access control using other methods and Express.
As a reference , here's the original announcement and FAQ:
Announcement: http://blog.centrify.com/introducing-centrify-server-suite-2014-1/
FAQ: http://www.centrify.com/express/linux-unix/faq/
Moderation Notice: Please never proactively submit support files to the public forums. The reasons are self-evident; we are a security company and unless obfuscation or de-identification techniques are used, you can potentially expose more information than needed. Bottom-line: Nobody from Centrify will request that you post debug information publicly.