Thank you for your response. In my API code I’m using different configuration data representing different Auth0 applications.
In my API code, I have:
"clientId": "CLIENT ID FOR ANGULAR SPA",
"audience": "AUDIENCE FOR API (this is the https://url-to-my-api)"
The above configurations are used with jwt.VerifyOptions with my ApolloGateway configuration. This is used to validate incoming Bearer tokens.
In my API code, I also have the following configurations set as env variables:
AUTH0_CLIENT_ID=CLIENT ID FOR Machine-To-Machine API Explorer
AUTH0_API=URL to my Auth0 Management API
The above configurations are used with creating a connection to Auth0’s management api in order for me to manually create a new user. This new user is being created and is somehow being connected to my API app instead of my Angular SPA app. I need my API to create a new user programmatically on behalf of my Angular SPA app.
My new Auth0 user being created via my API needs to receive an email pointing them to Angular SPA and not to API.
Should AUTH0_CLIENT_ID (which is currently configured to my API) really be configured as the client id of my Angular SPA Auth0 app?
In your response, you mentioned:
do you have its API identifier listed as the
audience in your app’s auth_config file?
When you say ‘your app’s auth_config file’, are you referring to my Angular SPA app, or my API app (because I have an auth_config file for each app)?