Short answer: No, unfortunately TIB currently only extracts those two fields for the proxy provider :-/
In TIB, the "provider" is separated from the "handler", and they interchange a uniform object
goth.User, the TIB Proxy provider currently only deserialises for the two name spaces (access token and user ID).
If you're up for some tinkering, it can be extended here:
(gabs is a handy little library that lets you access JSON using dot-notation). The
goth.User object is in the gothic library here:
We standardised o it because it works for all of the OAuth / Social connectors and encapsulates things quite nicely.
If you don't want to modify TIB (and I don't blame you), then the only thing I could think of doing is to serialise the full user data as a b64 string into the user-id field in your IDP so that you can extract it at your service layer, but that might not be very palatable.