When using a messaging deployment to create a knowledge portal only, how have you locked this down so it's only accessible to internal users if it is an internal KB?
It looks to me like when you query knowledge via the messaging SDK and a Knowledge portal. it consumes a separate set of /guest/ APIs. Domain locking the deployment doesn't really give a good level of security as that can be spoofed/bypassed.
I assume authentication in the messaging configuration is only for messaging itself and doesn't expand out to other services provided by the messaging SDK?
Interesting @VaunMcCarthy can you elaborate more on the use-case? Ideally, how would internal employees have access to the KB? Are you referring to agents, or rather having generic "signed-in" employees consuming a specific article variations, tailored to employees only? I'm trying to understand whether the signed-in employee would still use the same public website as an anonymous visitor, and if you would want to "tag" articles with a specific public/private flag.
As a solution for now you could rely on Variations based on Segments, and try to detect employee Sign-In on their current visit.
