No problem, I’m happy to help and thanks for confirming!
The opaque access token in this context is expected behavior due to the security risks associated with type of flow - Overall, this approach is not recommended for reasons mentioned in the link I referenced initially. The only potential “workaround” is to go through the IdP Initiated flow and then immediately follow it up with a prompt=none (silent authentication) request to /authorize - If consent has already been granted , this will let you get a valid JWT access token.
This is again not a recommended approach, but possible with additional work.
That’s great you were able to get the authorize request working in general - Would you mind sharing a HAR file with me directly wherein you capture this entire flow? I might be able to glean some information from the requests involved.
I’ll be honest in that I am not very familiar with this flow myself, but I’d expect to see a consent prompt.