OIDC: this user can't understand how to generate sub claim

[Cantor, Scott]

There has to be something preventing it from getting at that attribute, so either it's not getting resolved with any values, or that encoder rule isn't being applied.

The error just means what it says, there's no attribute with a rule to encode into a claim named "sub". It's an awkward approach, but that's how it's controlled.

Don't mess with the activation conditions, they're defined to get the right output in the various situations and you'll end up breaking the OP if you change them.

-- Scott