Can we include text in the spec and an example for custom_claim, example rs_auth_context. I believe we still have gaps in weaving complete AS context for the RAS, even with aud_tenant. Allowing for an optional custom claim in id-jag JWT will go along way to address this gap. I the custom claim is an object that has a flexible (key, value) or (format_specifier, key, value) presentation, it can be based on resource app config that is customized for the specific RAS.
Can we include text in the spec and an example for custom_claim, example
rs_auth_context. I believe we still have gaps in weaving complete AS context for the RAS, even withaud_tenant. Allowing for an optional custom claim in id-jag JWT will go along way to address this gap. I the custom claim is an object that has a flexible (key, value) or (format_specifier, key, value) presentation, it can be based on resource app config that is customized for the specific RAS.