Add AccessToken in response headers about traefik-forward-auth

[thomseddon]

Okie dokie, this shouldn't cause any issues so I'm game for working on this, I'll target 2.1

[thomseddon]

Hmm, to be honest, if you're going to the extent of working against the Google APIs then at that point, I think that this use case may actually be best served by created a forward authentication endpoint in your own application?

I'll leave this open for a while to see if there's any further support/justification but my current thinking is that this wouldn't be something we should support.

[tibkiss]

To one of our application it would be a requirement to pass the access token down to the service,
hence I second this ask.

oauth2_proxy is capable of both providing the access token and refreshing the token.

Unfortunately oauth2_proxy it is not integrating so elegantly with Traefik, traefik-forward-auth would be a much nicer solution if those two would be addressed.

[cstack89]

I think this may be a similar request, but sorry if it's not. But how hard would it be to only authenticate certain paths based on different scopes? Or add the users scope(s) to a header or something along those lines?

[thomseddon]

@cstack89 I think #57 and #63 should be what you're looking for

[thomseddon]

Note: if this option is enabled, the access token would need to be encrypted prior to storage in the cookie

[thomseddon]

I haven't found a elegant way to ensure backwards compatibility on this yet, so I'm going to push into 2.3

[thomseddon]

Notes added in #100 - hoping to merge that