When I use a Remote Service for distributed OSGi application I would like my provider to be able to implicitly pass some thread context like tracing IDs and also a user authorization token.
The OSGi compendium talks about implementation specific security based on codesigning, but not on thread identity (JAAS Context). Was there any plan to add something, like an interceptor mechanism? Some of it could be implementation specific, but some form of portable endpoint binding access would be nice, like peer-address, jaas-context, opentracing-id, maybe audit, tenant and request-ids? I can enrich my services with a Map<String,String> for most of it, however then there is no reliable way for the provider to add/ensure some of its protocol header properties and it hides the business interface under removing parameters. Gruss Bernd -- http://bernd.eckenfels.net
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
