Right, invoker already has the changes provided by the Entitlement spi. Additional variables are provided via `authEnvironment`val in the ContainerProxy.scala. Just want to point out that the new variables will be only available for the downstream implementations of the Entitlement SPI, e.g. IBM Functions.
regards, Vadim. On Mon, Aug 6, 2018 at 10:14 PM Carlos Santana <[email protected]> wrote: > There are no changes required to the invoker code to enable this, this is > already supported via SPI from what I understand, but Vadim can clarify > > -- Carlos > > On Mon, Aug 6, 2018 at 4:11 PM Carlos Santana <[email protected]> > wrote: > > > The runtime changes will allow a downstream like IBM Functions to > > implement the authentication and entitlement SPI already discussed in the > > mailing list by Martin, the controller will pass IAM (Identity and Access > > Management) data about the namespace to the invoker, and the invoker will > > pass this data to the runtimes as extra environment variables. > > > > -- Carlos > > > > > > On Mon, Aug 6, 2018 at 2:22 PM Rodric Rabbah <[email protected]> wrote: > > > >> > >> > So what are the invoker changes that will leverage these runtime > >> changes? I’m not sure that context was part of the thread yet, sorry if > it > >> was. > >> > >> It wasn’t but without invoker changes this in itself isn’t very useful. > >> You are right. > >> > >> -r > > > > >
