Thanks so much @josh.cunningham. Sorry if I wasn’t clear. I am putting together a new Angular 5 client which talks to a Laravel API - the Laravel Quickstart code from Github (linked to from the Quickstart guide). The Laravel API needs to persist users - there are various other tables related to users.
The MyCustomRepository provider in the Quickstart looks as if it should do exactly what I need (and in fact, in a previous applications did work using the code in the examples). However $profile referred to in the QuickStart does NOT contain any OIDC information - $profile now just contains the decrypted fields from the access_token. Given that Auth0 knows the user’s email, name, etc, I want to be able to save these in my Laravel API’s DB when the user first logs in. From reading around, it looks as if I will only be able to get this profile data from the id_token (which I have in my Angular client but not in the Laravel API).
So, as it stands, it looks as if the code in the Quickstart for Laravel APIs is now out of date (since Auth0 adopted the OIDC style of tokens?) and the code presented for MyCustomRepository no longer works?
So, my question is: how can I access the profile information which is contained in id_token from my Laravel api. Currently, I’m having to make a cURL call from MyCustomRepository to the Management API to get another access token which then allows me to get the user data - this seems very inefficient - is there a better way of doing this?
Many thanks
Damion