How do I keep C# enterprise identity separate from Montage authorization?
An enterprise identity assertion in a C# application is not automatic authorization to a Montage workspace. Review the outbound HTTP auth path independently of application sign-in so a familiar organizational account cannot conceal missing consent or unsafe cross-user credential reuse. The application must deliberately associate its authenticated caller with an approved Montage account. Organizational identity similarity cannot replace a supported remote grant, and private auth state should never be selected or disclosed through model-generated tool arguments.
Help me keep C# enterprise identity separate from Montage authorization. Identify the application’s authenticated caller and the Montage account intended to own the remote session. Report whether Montage authorized the intended read and preserve any separate application-auth outcome. No writes.Name the two identities
Identify the application’s authenticated caller and the Montage account intended to own the remote session. Treat that association as an application responsibility rather than assuming matching organization names establish a grant.
Review supported HTTP auth
Use the installed SDK’s documented authorization facilities and approved OAuth lifecycle where applicable. Do not forward enterprise assertions speculatively or reuse model-service credentials as a substitute for a Montage account authorization path.
Inspect private state ownership
Check that callback and credential storage belong to the requesting user and remain outside model prompts and shared logs. If account association is unsupported or ambiguous, leave the remote client unavailable instead of silently sharing access.
Test the outbound account
Execute signals_status directly through the configured client while its documented lifetime is valid. Read the actual workspace, not merely an application sign-in success or local identity claim that never reached Montage.
Return a domain-specific result
Report whether Montage authorized the intended read and preserve any separate application-auth outcome. A successful enterprise login does not certify workspace access or approve future remote changes, even when both systems serve the same organization.
Keep the boundaries clear.
- If account association is unsupported or ambiguous, leave the remote client unavailable instead of silently sharing access.
- A successful enterprise login does not certify workspace access or approve future remote changes, even when both systems serve the same organization.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.