Expose the current issuer

Search terms you've used

issuer

Impacted environment

In which environment would the proposed feature apply ?

• The browser
• Node.js
• Other (please specify): ...
• I'm not sure.

Feature suggestion

[...] "retrieve the current issuer from the session" [and] expose that via the ISessionInfo interface, potentially

In certain cases, it may be useful for an App to know the OIDC issuer which was used to authenticate current user.

E.g. a user with webId https://someuser.solidcommunity.net/profile/card#me may have an issuer https://solidcommunity.net, and we want to know that.

Expected functionality/enhancement

Currently, ISessionInfo doesn't expose issuer, and it could.
The issuer is exposed within the Authorization header of the fetch function as iss property of a JWT token. It's also exposed in localStorage, however i'm told this is going to change.

Actual functionality/enhancement

Expose the current issuer in ISessionInfo (or in other standard way)

Use Cases

• As of now, some OIDC Identity Providers (typically https://solidcommunity.net and other NSS-based servers) don't include solid:oidcIssuer in personal profile documents. This is sufficient for authenticating into NSS Pods, but fails when authenticating using e.g. @solid/access-token-verifier.
  So, sometimes an app needs to fix such incomplete profile document (if it can), to make it compliant. Hence, it needs to know the issuer.

• Also, perhaps an app wants to show the current issuer in UI... 🤷🏾‍♀️

ping @jeff-zucker

Start by reading the ISessionInfo interface and the fetch function documentation linked in the issue, then trace where session information and the Authorization header are assembled for browser and Node.js. Confirm how the issuer is currently represented and identify the relevant authentication tests or entry points. Done means the current OIDC issuer is exposed through the agreed session API and is covered for both environments.