To pass the API key into

/admin/identities

, you need to include it in the

Authorization

header of your API call. The API key should be prefixed with

Bearer

. Here's an example of how to do this:

bash GET /admin/identities HTTP/1.1   Host: $<http://PROJECT_SLUG.projects.oryapis.com|PROJECT_SLUG.projects.oryapis.com>   Accept: application/json   Authorization: Bearer $API_KEY

In this example, replace

$PROJECT_SLUG

with your project's slug and

$API_KEY

with your actual API key. Remember, API keys are used to authorize privileged operations to Ory Network Project Admin APIs. They work only in the context of the Project for which they were created. You can create API Keys in the [Ory Console](https://console.ory.sh/). For more information, refer to the [Ory documentation](https://www.ory.sh/docs/concepts/personal-access-token#authorizing-ory-network-project-admin-apis).

I'm sorry, but it seems like your question is not clear. Could you please provide more details or context? I'm here to help with questions related to Ory, a comprehensive open-source software infrastructure provider.

The error message you're seeing, "Requested url does not match any rules", typically occurs when the URL you're trying to access doesn't match any of the rules defined in your configuration. This could be due to a misconfiguration in your setup. If you're using Ory Kratos and you see this error after clicking on "Sign in with Auth0" or "Sign in with Salesforce", make sure that the "Tenant URL"/`issuer_url` is set correctly. You can find more information about this in the [Auth0 troubleshooting guide](https://www.ory.sh/docs/kratos/social-signin/auth0#troubleshooting) and the [Salesforce troubleshooting guide](https://www.ory.sh/docs/kratos/social-signin/salesforce#troubleshooting). If you're using Ory Hydra, there are a few steps you can take to debug the issue: 1. Check the logs. Ory Hydra has extensive logging and you will likely find the issue in the logs. 2. Check the URL. Ory Hydra sends

error_hint

,

error

,

error_description

,

error_debug

in the URL. You will likely find the cause of the error there. 3. Make sure the host, port, and path in the URL are correct. This is a common issue when you're just starting out and experimenting. 4. Set the environment variable

OAUTH2_EXPOSE_INTERNAL_ERRORS=true

. This will cause Ory Hydra to set the

error_debug

query parameter if debug information is available. However, don't do this in production as it could potentially leak important data. You can find more information about this in the [Hydra FAQ](https://www.ory.sh/docs/hydra/faq). If you're using Ory Oathkeeper, make sure your access rules are correctly configured. You can find more information about this in the [Oathkeeper documentation](https://www.ory.sh/docs/oathkeeper/configure-deploy#access-rules). If none of these solutions work, you may need to check your configuration or consult the relevant Ory documentation for more troubleshooting tips.