> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsiam-data-model-schema/consts/logon-type.md). # XDM\_CONST.LOGON\_TYPE A numeric value that indicates the type of logon session. See . | Original | Mapped | Description | | -------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 2 | XDM\_CONST.LOGON\_TYPE\_INTERACTIVE | Intended for users who are interactively using the machine, such as a user being logged on by a terminal server, remote shell, or similar process. | | 3 | XDM\_CONST.LOGON\_TYPE\_NETWORK | Intended for high-performance servers to authenticate clear text passwords. LogonUser does not cache credentials for this logon type. | | 4 | XDM\_CONST.LOGON\_TYPE\_BATCH | Intended for batch servers, where processes can be executed on behalf of a user without their direct intervention; or for higher performance servers that process many clear-text authentication attempts at a time, such as mail or web servers. LogonUser does not cache credentials for this logon type. | | 5 | XDM\_CONST.LOGON\_TYPE\_SERVICE | Indicates a service-type logon. The account provided must have the service privilege enabled. | | 6 | XDM\_CONST.LOGON\_TYPE\_PROXY | Indicates a proxy-type logon. | | 7 | XDM\_CONST.LOGON\_TYPE\_UNLOCK | This logon type is intended for GINA DLLs logging on users who are interactively using the machine. This logon type allows a unique audit record to be generated that shows when the workstation was unlocked. | | 8 | XDM\_CONST.LOGON\_TYPE\_NETWORK\_CLEARTEXT | Preserves the name and password in the authentication packages, allowing the server to make connections to other network servers while impersonating the client. This allows a server to accept clear text credentials from a client, call LogonUser, verify that the user can access the system across the network, and still communicate with other servers. | | 9 | XDM\_CONST.LOGON\_TYPE\_NEW\_CREDENTIALS | Allows the caller to clone its current token and specify new credentials for outbound connections. The new logon session has the same local identify, but uses different credentials for other network connections. | | 10 | XDM\_CONST.LOGON\_TYPE\_REMOTE\_INTERACTIVE | Terminal Services session that is both remote and interactive. | | 11 | XDM\_CONST.LOGON\_TYPE\_CACHED\_INTERACTIVE | Attempt cached credentials without accessing the network. | | 12 | XDM\_CONST.LOGON\_TYPE\_CACHED\_REMOTE\_INTERACTIVE | Same as RemoteInteractive. This is used for internal auditing. | | 13 | XDM\_CONST.LOGON\_TYPE\_CACHED\_UNLOCK | Workstation logon. | | 14 | XDM\_CONST.LOGON\_TYPE\_NON\_INTERACTIVE | Intended for users who are not interactively using a machine, such as users being logged not by a terminal server, remote shell, or similar process. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/xsiam-data-model-schema/consts/logon-type.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.