Thanks for the reply. My exclusion of the actual domain was on account of having this on a test server so it will change. I did try and add a context property to automate this, but couldn’t quite get it to work (I think because the property I was using had auth0 as the domain which is ignored).
Somethings like:
You were on the right track though you’ve made one small mistake which in my opinion is very easy to make as you have to read the docs very carefully, I made the same mistake as well.
The configuration properties do not live in the context object but instead live in a goal configuration object.
To show you what I mean here’s a simple rule from our system that adds the user’s email to the access_token:
Hmm, if you attach to idToken instead of accessToken, configuration.AUTH_NAMESPACE comes out as undefined which is a funny little quirk I came across in testing before because it does work. For some reason, unidentified is allowed through even through it doesn’t begin with https://
To answer your query about getting the access token, your request should have the responseType set to token id_token
In regards to the value coming our as undefined, have you made sure to add a configuration property to your rules? (The AUTH_NAMESPACE is not an inbuilt value, it’s a custom value)
You can do this in the Settings section of the Rules page in the Management dashboard.
Here’s a screenshot of some of our configurations that we have in our staging environment: