> ## Documentation Index > Fetch the complete documentation index at: https://docs-dev-docs-event-stream-action-templates.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > Learn about the properties of the Rules context object, which stores information about users' IP addresses, applications, and location. # Context Object Properties in Rules The End of Life (EOL) date of Rules and Hooks will be **November 18, 2026**, and they are no longer available to new tenants created as of **October 16, 2023**. Existing tenants with active Hooks will retain Hooks product access through end of life. We highly recommend that you use Actions to extend Auth0. With Actions, you have access to rich type information, inline documentation, and public `npm` packages, and can connect external integrations that enhance your overall extensibility experience. To learn more about what Actions offer, read [Understand How Auth0 Actions Work](/docs/customize/actions/actions-overview). To help with your migration, we offer guides that will help you [migrate from Rules to Actions](/docs/customize/actions/migrate/migrate-from-rules-to-actions) and [migrate from Hooks to Actions](/docs/customize/actions/migrate/migrate-from-hooks-to-actions). We also have a dedicated [Move to Actions](https://auth0.com/extensibility/movetoactions) page that highlights feature comparisons, [an Actions demo](https://www.youtube.com/watch?v=UesFSY1klrI), and other resources to help you on your migration journey. To read more about the Rules and Hooks deprecation, read our blog post: [Preparing for Rules and Hooks End of Life](https://auth0.com/blog/preparing-for-rules-and-hooks-end-of-life/). The `context` object stores contextual information about the current authentication transaction, such as the user's IP address, application, or location. If you change token content using the context object within a rule, your changes will be available in tokens after all rules have finished running. If your application also requires multifactor authentication or user consent, the user will be prompted before changes in the token are available. ## Properties The following properties are available for the `context` object. | Property | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `context.tenant` | A string containing the name of the tenant. | | `context.clientID` | The client id of the application the user is logging in to. | | `context.clientName` | The name of the application (as defined on the dashboard). | | `context.clientMetadata` | An object for holding other application properties. Its keys and values are strings. | | `context.connectionID` | A string containing the connection's unique identifier. | | `context.connection` | The name of the connection used to authenticate the user (such as: `twitter` or `some-g-suite-domain`) | | `context.connectionStrategy` | The type of connection. For social connection `connectionStrategy` === `connection`. For enterprise connections, the strategy will be `waad` (Windows Azure AD), `ad` (Active Directory/LDAP), `auth0` (database connections), and so on. | | `context.connectionOptions` | An object representing the options defined on the connection. `connectionOptions.tenant_domain` is a string containing the domain being used for authentication when using an Enterprise connection.
`connectionOptions.domain_aliases` is an array containing the optional domains registered as aliases in addition to the primary domain (specified in the `connectionOptions.tenant_domain` property). | | `context.connectionMetadata` | An object representing metadata defined on the connection. Its keys and values are strings. | | `context.samlConfiguration` | An object that controls the behavior of the [SAML](/docs/glossary?term=SAML) and WS-Fed endpoints. Useful for advanced claims mapping and token enrichment (only available for `samlp` and `wsfed` protocol). | | `context.protocol` | The authentication protocol. Possible values: | | `context.riskAssessment` | An object containing specific scores (low, medium, high, neutral) for high risk login attempt assessors. See [Customize Adaptive MFA with Rules](/docs/secure/multi-factor-authentication/adaptive-mfa/customize-adaptive-mfa). | | `context.stats` | An object containing specific user stats, like `stats.loginsCount`. Note that any of the counter variables returned as part of the `stats` object do not increase during [silent authentication](/docs/authenticate/login/configure-silent-authentication) (as when `prompt=none`). There are also scenarios where the counter variables might increase yet a rule or set of rules do not execute, as in the case of a successful cross-origin authentication followed by a failed token request. | | `context.sso` | This object will contain information about the [Single Sign-on (SSO)](/docs/glossary?term=Single+Sign-on+%28SSO%29) transaction (if available) | | `context.accessToken` | An object representing the options defined on the [Access Toke](/docs/glossary?term=Access+Toke). You can use this object to [add custom namespaced claims](/docs/get-started/apis/scopes/sample-use-cases-scopes-and-claims#add-custom-claims-to-a-token) to the [Access Toke](/docs/glossary?term=Access+Toke). `context.accessToken.scope` can be used to [change the Access Token's returned scopes](/docs/customize/actions/actions-overview#modify-scope-of-access-token). When provided, it is an array containing permissions in string format. Custom claims will be included in the Access Token after all rules have run. | | `context.idToken` | An object representing the options defined on the [ID Token](/docs/secure/tokens/id-tokens). Used to add custom [namespaced](/docs/secure/tokens/json-web-tokens/create-custom-claims) claims to the ID Token. Custom claims will be included in the ID Token after all rules have run. | | `context.multifactor` | An object representing the multifactor settings used in [implementing contextual MFA](/docs/secure/multi-factor-authentication). | | `context.redirect` | The object used to [implement the redirection of a user from a rule](/docs/customize/rules/redirect-users#how-to-implement-a-redirect). | | `context.sessionID` | An internal identification for the authentication session. Value is kept only if `prompt=none` is used in the authorization request. Note that the session ID can change **after** rule execution on other flows, so the value available in `context.sessionID` might not match the new session ID that the user will receive. This makes this value only meaningful when `prompt=none` is used. | | `context.request` | An object containing useful information of the request. This can also be set to `undefined`. It has the following properties: | | `context.primaryUser` | The unique user id of the primary account for the user. Used to [link user accounts](/docs/manage-users/user-accounts/user-account-linking#automatic-account-linking) from various identity providers. | | `context.authentication` | An object containing information related to the authentication transaction with the following properties:

`methods`: an array of objects containing the authentication methods a user has completed during their session. For example, a user that has completed a password-based authentication followed by MFA may have the following methods:
`json lines [ { "name": "pwd", "timestamp": 1434454643024 }, { "name": "mfa", "timestamp": 1534454643881 } ] `
The method objects will contain the following properties: You can see a sample use case of the `context.authentication.methods` property in the [Require MFA once per session Rule](https://github.com/auth0/rules/blob/master/src/rules/require-mfa-once-per-session.js). | | `context.authorization` | An object containing information related to the authorization transaction with the following properties: | | `context.organization` | Object containing information related to the organization. Includes the following properties: | ## Learn more * [Debug Rules](/docs/customize/rules/debug-rules) * [User Object Properties in Rules](/docs/customize/rules/user-object-in-rules) * [Sample Use Cases: Scopes and Claims](/docs/get-started/apis/scopes/sample-use-cases-scopes-and-claims)