Re: [Architecture] [APIM][C5] Application Import Export feature for Api Manager 3.0.0

Hi Krishan, The feature supports non admin users as well, any user with the exported zip file within the apim subscribe scope can import the application to any environment. On Mon, Nov 20, 2017 at 12:05 PM, Krishan Wijesena wrote: > Hi Randilu, > >> >> On Tue, Nov 14, 2017

Re: [Architecture] [APIM][C5] Application Import Export feature for Api Manager 3.0.0

Hi Randilu, > > On Tue, Nov 14, 2017 at 4:56 PM, Randilu Soysa wrote: > >> Hi, >> >> >> Im working on Application Import Export feature for APIM 3.0.0 in order >> to migrate an application to different environments. Two REST endpoints >> were implemented to export an

Re: [Architecture] [IS] Supplementary OSGi service for adding new claims to ID Token

Hi Piraveena, +1 For the OIDC hybrid flow implementation c_hash value should be injected to id_token and I can use this new service for that. Thanks. On Mon, Nov 20, 2017 at 10:46 AM, Piraveena Paralogarajah < pirave...@wso2.com> wrote: > Hi all, > > According to the current implementation,

[Architecture] [IS] Supplementary OSGi service for adding new claims to ID Token

Hi all, According to the current implementation, there is no way to inject claims into ID Token without changing the existing code base. So there are some case where we need to insert claims to ID token for some specific purposes. For an example, In OpenID Connect Back-channel logout, sid claim

Re: [Architecture] Workday Connector

Hi Nirthika, I guess the TimeoutHandler message is not actually an error. It shouldn't cause any issues because it's just getting logged when the blocking message sender is invoked inside the call-out mediator. Thanks. On Sun, Nov 19, 2017 at 7:29 PM, Nirthika Rajendran

Re: [Architecture] Workday Connector

Hi All, In the workday connector implementation username-token is used for the authentication. Accoding to [1] for the blocking mode I use callout mediator [2] as below. But I am getting "Error in extracting message properties" and "TimeoutHandler This engine will expire all callbacks

Re: [Architecture] [Deployment] [Puppet] Upgrading WSO2 Puppet Modules to Puppet 5.x from 3.x

On Fri, Nov 17, 2017 at 5:59 PM, Dilan Udara Ariyaratne wrote: > > It was possible to fix this remaining issue by accessing the manifest > variables in .erb files using the scope['variable'] notation [1] instead of > the existing @variable local scope notation [2]. > With this