Is getSession not supposed to work with OAuth?

[snarfed]

Hi all! I'm finishing up an OAuth client implementation, and I noticed that I can use a DPoP token with most authed XRPC endpoints, but not com.atproto.server.getSession. I get HTTP 400 DPoP requests cannot be proxied. Looks like this is expected:

DPoP requests are bound to the endpoint being called. Allowing them to be
proxied would require that the receiving end allows DPoP proof not
created for him. Since proxying is mainly there to support legacy
clients, and DPoP is a new feature, we don't support DPoP requests
through the proxy.

This is fine since app views are usually called using the requester's
credentials when "auth.credentials.type === 'access'", which is the only
case were DPoP is used.

I'm not sure how to interpret that. I'm not trying to proxy anything; I'm making the getSession call directly to my PDS, eg https://enoki.us-east.host.bsky.network/xrpc/com.atproto.server.getSession. Is getSession just not supported with OAuth? If not, is there a recommended way to get the current session's status, DID, etc?

Thanks in advance!

[matthieusieben]

We currently don't have a way to get a user's info when they are logged in through OAuth. This is a known limitation and it is in our backlog for the next quarter. Sorry for the inconvenience.

Note

The technical reason is that sessions are not managed by the PDS, but rather by the "entryway". Because of that, the PDS will not handle getSession itself but rather proxy the request to the "entryway". Since proxying is not compatible with DPoP proofs, you get this error.

[snarfed]

Thanks @matthieusieben! Understood, no worries. I can get the authenticated DID from sub and use the refresh token flow like usual when I need to.