use trace id of external service

[hifabienne]

Describe your problem

The oidc lib currently always creates a root span even though my service already provides a trace id. I currently have to correlate the two traces manually which is error prone and maybe the call doesn't even get traced if the fraction does not match.

Describe your ideal solution

If my service uses tracing i want to be able provide this traceid to zitadel so that i can see the zitadel calls as sub spans.

[muhlemmer]

The issue here is that the utilities we need for the behavior you describe are in zitadel and therefore cannot be imported into oidc. Now that we have v3 in zitadel and we will implement all methods directly (deprecating the storage interface) the traces should get better in time.

If you think we need to improve this earlier, we will have to see if we can abstract or duplicate some of the trace code from zitade.

[hifabienne]

hei @muhlemmer
Thanks for the feedback.
This issue was raised by a client who uses our oidc lib in their own application, where they also want to be able to set the trace ids