Re: [Architecture] [APIM][C5] Multi-Environment API Overview Feature

On Wed, Jan 24, 2018 at 6:12 PM, Sanjeewa Malalgoda wrote: > If one environment trust the user then cant we assume other environment > which trust initial environment can also accept this as valid user. > This is a valid point IMHO. Haven't we evaluated the possibility of

Re: [Architecture] [APIM][C5] Multi-Environment API Overview Feature

If one environment trust the user then cant we assume other environment which trust initial environment can also accept this as valid user. We can even use certificate based grant type of implementation. Then use login to one environment successfully that environment should be able to obtain token

Re: [Architecture] [APIM][C5] Multi-Environment API Overview Feature

Hi all, We are going to authenticate the user to other environments via JWT grant type [1]. The feature is disabled by default and the below configuration is going to be used to enable the feature. If JWT grant type is not supported by the IDP, the user can use a similar grant as an extension

[Architecture] [APIM][C5] Multi-Environment API Overview Feature

Hi All, We are planning to implement a feature that enables the users to get the Multi-Environment API Overview of APIs that they are managing across multi environments. Please refer the GitHub issue[1]. Appreciate any suggestions and comment on the Github issue about your suggestions. [1]

Re: [Architecture] [APIM][C5] Multi-Environment API Overview Feature

Hi Pubudu, Details are in the github issue. It is not about API Implementation level diff. It is showing overview of how APIs are deployed in different environments. Eg. What are the APIs, API version, Lifecycle state in dev, test, prod environment etc. It is API management overview across multi

Re: [Architecture] [APIM][C5] Multi-Environment API Overview Feature

Hi Renuka, What are we planning to display in 'Multi-Environment API Overview'? Could you please elaborate more on this? Are we showing the diff in each environment? Thank you! On Tue, Jan 9, 2018 at 12:58 PM, Renuka Fernando wrote: > Hi All, > > We are planning to implement