Gotcha, I will keep this in mind if anymore issues arise as a potential path to explore.
Actually, what I ended up doing shortly after I made my 2nd post last week was downloading and digging into source code of composite and I saw where they "DENIED" line gets generated within the following module:
Thanks for the response!
Actually, what I ended up doing shortly after I made my 2nd post last week was downloading and digging into source code of composite and I saw where they "DENIED" line gets generated within the following module:
<add name="CompositeAdministrativeAuthorization" type="Composite.Core.WebClient.HttpModules.AdministrativeAuthorizationHttpModule, Composite" />
So I commented that out and all seems to be going well, no more reported issues from my client so far. Like I mentioned in my first post, I'm using the Active Directory plug-in for login to the Composite Admin, because of that I'm assuming the cookie is never generated (and isn't really needed). Figured removing the use of the module all together wouldn't hurt anything and it's been a week and there hasn't been any adverse effects reported.Thanks for the response!