Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC2
gt;>>>>>- Tested Analytics dashboard manage >>>>>>> >>>>>>> [+] Stable - go ahead and release >>>>>>> >>>>>>> On Sat, 8 Aug 2020 at 22:59, Tharindu Dharmarathna < >>>>>>> tharin...@wso2.com> wrote: >>>>>>> >>>>>>>> Tested the following flow for the tenant and super tenant users. >>>>>>>> >>>>>>>> - Okta Integration >>>>>>>> >>>>>>>> No issues found. +1 to proceed with the release. >>>>>>>> >>>>>>>> >>>>>>>> On Sat, Aug 8, 2020 at 6:36 PM Mushthaq Rumy >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Tested the following flows for super tenant and tenant users. >>>>>>>>> - Basic flow of API creation, subscription and invocation >>>>>>>>> - Soap API with pass through >>>>>>>>> - Soap to Rest feature >>>>>>>>> >>>>>>>>> No issues found. +1 to proceed with the release. >>>>>>>>> >>>>>>>>> Thanks & Regards, >>>>>>>>> Mushthaq >>>>>>>>> >>>>>>>>> On Sat, Aug 8, 2020 at 5:53 PM Amila De Silva >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Tested Artifact Synchroniser for Super Tenant mode >>>>>>>>>> - for Basic flows >>>>>>>>>> - With multiple Labels assigned to APIs >>>>>>>>>> - Startup Delay configured >>>>>>>>>> - for failover scenarios (On a Setup with GWs without DB access >>>>>>>>>> and TMs in Failover mode) >>>>>>>>>> No issues found. >>>>>>>>>> >>>>>>>>>> +1 to proceed with the release. >>>>>>>>>> >>>>>>>>>> On Sat, Aug 8, 2020 at 12:25 PM Arshardh Ifthikar < >>>>>>>>>> arsha...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> We are pleased to announce the second release candidate of WSO2 >>>>>>>>>>> API Manager 3.2.0. >>>>>>>>>>> >>>>>>>>>>> This release fixes the following issues. >>>>>>>>>>> >>>>>>>>>>>- Fixes : product-apim >>>>>>>>>>> >>>>>>>>>>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-08-06> >>>>>>>>>>>- Fixes : analytics-apim >>>>>>>>>>><https://github.com/wso2/analytics-apim/milestone/28?closed=1> >>>>>>>>>>> >>>>>>>>>>> Source and distribution, >>>>>>>>>>> Runtime : >>>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc2 >>>>>>>>>>> Analytics : >>>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc2 >>>>>>>>>>> >>>>>>>>>>> Documentation : https://apim.docs.wso2.com/en/3.2.0/ >>>>>>>>>>> Migration docs : >>>>>>>>>>> https://apim.docs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/ >>>>>>>>>>> >>>>>>>>>>> Please download, test the product and vote. >>>>>>>>>>> >>>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> WSO2 API Manager Team >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> *Arshardh Ifthikar* >>>>>>>>>>> Senior Software Engineer | WSO2 Inc. >>>>>>>>>>> >>>>>>>>>>> Email: arsha...@wso2.com >>>>>>>>>>> Mobile: +94777218551 >>>>>>>>>>> Web: http://wso2.com >>>>>>>>>>> >>>>>>>>>>> <http://wso2.com/signature> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Amila De Silva* >>>>>>>>>> Software Architect | Associate Director, Engineering - WSO2 Inc. >>>>>>>>>> (m) +94 775119302 | (e) ami...@wso2.com >>>>>>>>>> <http://wso2.com/signature> >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Mushthaq Rumy >>>>>>>>> *Associate Technical Lead* >>>>>>>>> Mobile : +94 (0) 779 492140 >>>>>>>>> Email : musht...@wso2.com >>>>>>>>> WSO2, Inc.; http://wso2.com/ >>>>>>>>> lean . enterprise . middleware. >>>>>>>>> >>>>>>>>> <http://wso2.com/signature> >>>>>>>>> ___ >>>>>>>>> Architecture mailing list >>>>>>>>> architect...@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Tharindu Dharmarathna*Technical Lead >>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> mobile: *+94779109091* >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. >>>>>>> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com >>>>>>> GET INTEGRATION AGILE >>>>>>> Integration Agility for Digitally Driven Business >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> architect...@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> >>>> * Shammi Jayasinghe* >>>> >>>> >>>> *Associate Director/ Architect* >>>> *WSO2, Inc.* >>>> *+1-812-391-7730* >>>> *+1-812-327-3505* >>>> >>>> *http://shammijayasinghe.blogspot.com >>>> <http://shammijayasinghe.blogspot.com>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> Thanks & Regards >>> >>> *Chaminda Jayawardena* >>> WSO2 Inc. - http://wso2.com >>> +94-77-7725234 >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Nadee Poornima* > Software Engineer - Support Team | WSO2 > > Email : nad...@wso2.com > Mobile : +94713441341 > MyBlog: https://medium.com/nadees-tech-stories > > <https://wso2.com/signature> > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Sachini De Silva* Senior Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.1.0 RC3
analytics-apim/releases/tag/v3.1.0-rc3 >>>>>>>>>>> >>>>>>>>>>> Please download, test the product and vote. >>>>>>>>>>> >>>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> WSO2 API Manager Team >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> *Krishan Wijesena* >>>>>>>>>>> Senior Software Engineer | WSO2 >>>>>>>>>>> >>>>>>>>>>> Email : krish...@wso2.com >>>>>>>>>>> Mobile : +94776219923 >>>>>>>>>>> WSO2 Inc : http://wso2.com >>>>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *Tharindu Dharmarathna*Technical Lead >>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>> lean.enterprise.middleware >>>>>>>>>> >>>>>>>>>> mobile: *+94779109091* >>>>>>>>>> ___ >>>>>>>>>> Dev mailing list >>>>>>>>>> Dev@wso2.org >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Sanjula Madurapperuma* | Software Engineering Intern | WSO2 Inc. >>>>>>>>> (m) +94 768877766 | (e) sanj...@wso2.com >>>>>>>>> <http://wso2.com/signature> >>>>>>>>> ___ >>>>>>>>> Architecture mailing list >>>>>>>>> architect...@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Nuwan Dias* | Senior Director | WSO2 Inc. >>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Krishan Wijesena* >>>>>>> Senior Software Engineer | WSO2 >>>>>>> >>>>>>> Email : krish...@wso2.com >>>>>>> Mobile : +94776219923 >>>>>>> WSO2 Inc : http://wso2.com >>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Krishan Wijesena* >>>>>> Senior Software Engineer | WSO2 >>>>>> >>>>>> Email : krish...@wso2.com >>>>>> Mobile : +94776219923 >>>>>> WSO2 Inc : http://wso2.com >>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> architect...@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>> >>>>> >>>>> -- >>>>> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. >>>>> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com >>>>> GET INTEGRATION AGILE >>>>> Integration Agility for Digitally Driven Business >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc. >>>> +94 710 618 178 >>>> GET INTEGRATION AGILE >>>> Integration Agility for Digitally Driven Business >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Vithursa Mahendrarajah* | Senior Software Engineer | WSO2 Inc >> (m) +94 766 695 643 | (e) vithu...@wso2.com >> >> * <http://wso2.com/signature>[image: https://wso2.com/signature] >> <https://wso2.com/signature>* >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Kavishka Fernando* > *Senior Software Engineer | WSO2* > Email: kavis...@wso2.com > Mobile: +94773838069 > Web: http://wso2.com > Blog: https://medium.com/@kavishkafernando > > <http://wso2.com/signature> > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Sachini De Silva* Senior Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] API Categories
@Harsha Kumara will switch to tenant id.
@Nuwan Dias +1 will add a single scope
‘apim:api_category’ to do all api categories related operations.
In publisher, categories/ GET resource can be associated with apim:api_view
scope. In store we can avoid attaching a scope to categories/ GET resource
and allow to access the resource without a token.
On Wed, Nov 13, 2019 at 11:50 AM Nuwan Dias wrote:
> For the admin API, I don't think we need separate scopes for the read and
> write of categories, isn't it?
>
> The publisher and store APIs would also need an API each to fetch the
> categories. These can be bound to already available scopes I assume.
>
> On Wed, Nov 13, 2019 at 11:26 AM Sachini De Silva
> wrote:
>
>> +1
>>
>> On Wed, Nov 13, 2019 at 11:13 AM Bhathiya Jayasekara
>> wrote:
>>
>>> Shall we use "API Categories" everywhere instead of just "Categories"?
>>> Because in the future there can be other category types too.
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Wed, Nov 13, 2019 at 10:59 AM Sachini De Silva
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I am working on a new feature ‘API Categories’. It is very similar to
>>>> tag wise grouping in store from a store UI POV but has the following
>>>> differences w.r.t tags.
>>>> 1. Categories define a broader collection of APIs. Tags can be used by
>>>> the publisher to emphasize specific details of an API.
>>>> 2. Categories have to be pre-defined by an Admin before they can be
>>>> associated with any APIs.
>>>> 3. Categories can have any valid string as their category name. Whereas
>>>> tag wise groups must have the suffix -group to be identified as a tag
>>>> group.
>>>>
>>>> In order to support this in APIM, I thought of using the following
>>>> approach.
>>>> 1. Define a REST API to do operations on category resources. Sample GET
>>>> and POST resources would be as below.
>>>>
>>>> *"/categories"*: { *"get"*: {*"x-scope"*: *"apim:category_read"*,
>>>> *"x-wso2-request"*: *"GET
>>>> https://localhost:9443/api/am/admin/v0.15/categories
>>>> <https://localhost:9443/api/am/admin/v0.15/categories>**\n**Authorization:
>>>> Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8**\n**"*,*"x-wso2-curl"*:
>>>> *"curl -k -H **\"**Authorization: Bearer
>>>> ae4eae22-3f65-387b-a171-d37eaa366fa8**\"
>>>> \"**https://localhost:9443/api/am/admin/v0.15/categories
>>>> <https://localhost:9443/api/am/admin/v0.15/categories>**\"**"*,
>>>> *"x-wso2-response"*: *"HTTP/1.1 200 OK**\r\n**Content-Type:
>>>> application/json**\r\n\r\n**{**\r\n \"**count**\"**:1,**\r\n
>>>> \"**list**\"**:[**\r\n* *{**\r\n
>>>> \"**id**\"**:**\"**463e2c9f-5e99-43c3-a66e-de7e0f367373**\"**,**\r\n
>>>> \"**name**\"**:**\"**Finance**\"**,**\r\n
>>>> \"**description**\"**:**\"**Finance related APIS**\"\r\n* *}**\r\n*
>>>> *]**\r\n**}"*,*"summary"*: *"Get all API categories"*,
>>>> *"description"*: *"Get all API categories**\n**"*,*"tags"*: [
>>>> *"Category Collection"*],*"responses"*: { *"200"*: {
>>>> *"description"*: *"OK.**\n**Categories returned**\n**"*,
>>>> *"schema"*: { *"$ref"*: *"#/definitions/**Category**List"*
>>>> } }} }, *"post"*: {*"x-scope"*: *"apim:category_manage"*,
>>>> *"x-wso2-curl"*: *"curl -k -X POST -H **\"**Authorization: Bearer
>>>> 0d63e133-7ad6-3aeb-9ca9-9299e0708122**\"* *-H **\"**Content-Type:
>>>> application/json**\"* *https://apis.wso2.com/api/am/admin/v0.15/
>>>> <https://apis.wso2.com/api/am/admin/v0.15/>**categorie**s -d @data.json"*,
>>>>*"x-wso2-request"*: *"POST
>>>> https://localhost:9443/api/am/admin/v0.15/categories
>>>> <https://localhost:9443/api/am/admin/v0.15/categories>**\r\n**Authorization:
>>>> Bearer 0d63e133-7ad6-3aeb-9ca9-9299e0708122**\r\n**C
Re: [Dev] [APIM] API Categories
+1
On Wed, Nov 13, 2019 at 11:13 AM Bhathiya Jayasekara
wrote:
> Shall we use "API Categories" everywhere instead of just "Categories"?
> Because in the future there can be other category types too.
>
> Thanks,
> Bhathiya
>
> On Wed, Nov 13, 2019 at 10:59 AM Sachini De Silva
> wrote:
>
>> Hi all,
>>
>> I am working on a new feature ‘API Categories’. It is very similar to tag
>> wise grouping in store from a store UI POV but has the following
>> differences w.r.t tags.
>> 1. Categories define a broader collection of APIs. Tags can be used by
>> the publisher to emphasize specific details of an API.
>> 2. Categories have to be pre-defined by an Admin before they can be
>> associated with any APIs.
>> 3. Categories can have any valid string as their category name. Whereas
>> tag wise groups must have the suffix -group to be identified as a tag group.
>>
>> In order to support this in APIM, I thought of using the following
>> approach.
>> 1. Define a REST API to do operations on category resources. Sample GET
>> and POST resources would be as below.
>>
>> *"/categories"*: { *"get"*: {*"x-scope"*: *"apim:category_read"*,
>> *"x-wso2-request"*: *"GET
>> https://localhost:9443/api/am/admin/v0.15/categories
>> <https://localhost:9443/api/am/admin/v0.15/categories>**\n**Authorization:
>> Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8**\n**"*,*"x-wso2-curl"*:
>> *"curl -k -H **\"**Authorization: Bearer
>> ae4eae22-3f65-387b-a171-d37eaa366fa8**\"
>> \"**https://localhost:9443/api/am/admin/v0.15/categories
>> <https://localhost:9443/api/am/admin/v0.15/categories>**\"**"*,
>> *"x-wso2-response"*: *"HTTP/1.1 200 OK**\r\n**Content-Type:
>> application/json**\r\n\r\n**{**\r\n \"**count**\"**:1,**\r\n
>> \"**list**\"**:[**\r\n* *{**\r\n
>> \"**id**\"**:**\"**463e2c9f-5e99-43c3-a66e-de7e0f367373**\"**,**\r\n
>> \"**name**\"**:**\"**Finance**\"**,**\r\n
>> \"**description**\"**:**\"**Finance related APIS**\"\r\n* *}**\r\n*
>> *]**\r\n**}"*,*"summary"*: *"Get all API categories"*,
>> *"description"*: *"Get all API categories**\n**"*,*"tags"*: [
>> *"Category Collection"*],*"responses"*: { *"200"*: {
>> *"description"*: *"OK.**\n**Categories returned**\n**"*,*"schema"*:
>> { *"$ref"*: *"#/definitions/**Category**List"*} }}
>> }, *"post"*: {*"x-scope"*: *"apim:category_manage"*,
>> *"x-wso2-curl"*: *"curl -k -X POST -H **\"**Authorization: Bearer
>> 0d63e133-7ad6-3aeb-9ca9-9299e0708122**\"* *-H **\"**Content-Type:
>> application/json**\"* *https://apis.wso2.com/api/am/admin/v0.15/
>> <https://apis.wso2.com/api/am/admin/v0.15/>**categorie**s -d @data.json"*,
>> *"x-wso2-request"*: *"POST
>> https://localhost:9443/api/am/admin/v0.15/categories
>> <https://localhost:9443/api/am/admin/v0.15/categories>**\r\n**Authorization:
>> Bearer 0d63e133-7ad6-3aeb-9ca9-9299e0708122**\r\n**Content-Type:
>> application/json**\r\n\r\n* *-d {**\r\n
>> \"**name**\"**:**\"**Finance**\"**,**\r\n
>> \"**description**\"**:**\"**Finance related APIS**\"\r\n* *}"*,
>> *"x-wso2-response"*: *"HTTP/1.1 201 Created**\r\n**Content-Type:
>> application/json**\r\n\r\n**{**\r\n \"**count**\"**:1,**\r\n
>> \"**list**\"**:[**\r\n* *{**\r\n
>> \"**id**\"**:**\"**463e2c9f-5e99-43c3-a66e-de7e0f367373**\"**,**\r\n
>> \"**name**\"**:**\"**Finance**\"**,**\r\n
>> \"**description**\"**:**\"**Finance related APIS**\"\r\n* *}**\r\n*
>> *]**\r\n**}"*,*"summary"*: *"Add a Category"*,*"description"*: *"Add
>> a new API Category**\n**"*,*"parameters"*: [ {*"in"*:
>> *"body"*,*"name"*: *"body"*,*"description"*: *"Category
>> object that should to be added**\n**"*,*"required"*: *true*,
>
[Dev] [APIM] API Categories
uot;example"*:
*"01234567-0123-0123-0123-012345678901"* }, *"name"*: {
*"type"*: *"string"*,*"example"*: *"Finance"* },
*"description"*: {*"type"*: *"string"*,*"example"*:
*"Finance related APIs"* }} }, *"CategoryList"*: {
*"title"*: *"Category List"*,*"properties"*: { *"count"*: {
*"type"*: *"integer"*,*"description"*: *"Number of
categories returned.**\n**"*,*"example"*: 1 },
*"list"*: {*"type"*: *"array"*,*"items"*: {
*"$ref"*: *"#/definitions/Category"*} }} }}
2. Define a new AM_CATEGORIES table to hold category related details.
*CREATE TABLE *IF *NOT EXISTS *AM_CATEGORIES ( CATEGORY_ID
*VARCHAR*(50), NAME *VARCHAR*(255), DESCRIPTION *VARCHAR*(1024),
TENANT_DOMAIN *VARCHAR*(255), *UNIQUE *(NAME,TENANT_DOMAIN),
*PRIMARY KEY *(CATEGORY_ID));
3. Publisher UI overview tab(or a suitable place as it fits) will have a
new UI element to select categories for the API. And selecting categories
for an API would be optional.
4. API to category mapping will be stored in registry API artifact and for
that following table field would have to be added to api.rxt. (I assume we
are going to support associating a single API with multiple categories)
Category Name
categoryName
5. And from store viewing POV, I assume API categories are a substitution
for existing tag-wise grouping feature and that both tag-wise groups and
categories won’t co-exist in the store. Please do correct if my
understanding is wrong.
Once a developer visits the store, he will be presented with the list of
API categories and upon selecting a category out of those, associated APIs
will be listed.
APIs that are not associated with any category will be listed under other
APIs or a similar heading.
Please feel free to add your suggestions.
Thanks,
Sachini
--
*Sachini De Silva*
Senior Software Engineer - WSO2
Email : sachi...@wso2.com
Mobile : +94714765495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC3
Hi, I have tested the following. - Application Attributes - Cross tenant API subscription and invocation - Subscription blocking - Store theming No blockers found. Hence +1 to go ahead and release. Thanks, Sachini On Fri, Oct 25, 2019 at 1:23 PM Dushan Silva wrote: > Hi, > I have tested the following > Authorization code grant type, > JWT grant type, > NTLM grant type, > Password grant type, > Client credentials grant type, > > Provisioning Out-of-Band OAuth Clients > Application group sharing > self registration > > No blockers found. +1 to go ahead and release. > > > > On Fri, Oct 25, 2019 at 12:20 PM Chamin Dias wrote: > >> Hi, >> >> Tested the following scenarios in both the super tenant and tenant. >> - API keys for securing APIs >> - Localization / internationalisation >> - Monetization (with in-built implementation) >> >> No blockers found. Hence, [+] Stable: go ahead and release. >> >> Thanks. >> >> On Fri, Oct 25, 2019 at 11:28 AM Mushthaq Rumy wrote: >> >>> Hi All, >>> >>> Hi All, >>> >>> Tested the following scenarios in both super tenant and tenant. >>> - API Creation, Publishing, Subscribing and invocation of APIs >>> - Tested Publisher Access Control >>> - Tested Store Visibility >>> - Identity management features such as self sign up, password reset, >>> password policy, account locking. >>> >>> No blockers found. Hence, [+] Stable - go ahead and release. >>> >>> Thanks & Regards, >>> Mushthaq >>> >>> On Fri, Oct 25, 2019 at 3:52 AM Samitha Chathuranga >>> wrote: >>> >>>> Hi All, >>>> >>>> We are pleased to announce the second release candidate of WSO2 API >>>> Manager 3.0.0. >>>> >>>> This release fixes the following issues. >>>> >>>>- Fixes : product-apim >>>> >>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24> >>>>- Fixes : carbon-apimgt >>>> >>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24+> >>>>- Fixes : analytics-apim >>>> >>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24> >>>> >>>> Source and distribution, >>>> Runtime : >>>> https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc3 >>>> Analytics : >>>> https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc3 >>>> APIM Tooling : >>>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc >>>> >>>> Please download, test the product and vote. >>>> >>>> [+] Stable - go ahead and release >>>> [-] Broken - do not release (explain why) >>>> >>>> Thanks, >>>> WSO2 API Manager Team >>>> >>>> >>>> -- >>>> *Samitha Chathuranga* >>>> *Senior Software Engineer*, *WSO2 Inc.* >>>> lean.enterprise.middleware >>>> Mobile: +94715123761 >>>> >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>> >>> >>> -- >>> Mushthaq Rumy >>> *Senior Software Engineer* >>> Mobile : +94 (0) 779 492140 >>> Email : musht...@wso2.com >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middleware. >>> >>> <http://wso2.com/signature> >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> -- >> Chamin Dias >> Mobile : 0716097455 >> Email : cham...@wso2.com >> LinkedIn : https://www.linkedin.com/in/chamindias >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > Best Regards > Dushan Silva > Software Engineer > > *WSO2, Inc. * > > lean . enterprise . middleware > Mob: +94 774 979042 > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Sachini De Silva* Senior Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Transfer API manager 2.1 swagger.json files to API manager 2.6
Hi Bernard, APIM 2.1.0 supports swagger version 2.0 and initially, we had implemented only a json validation against the uploaded swagger definitions. As an improvement, we have introduced a swagger spec validation to block uploading invalid swagger definitions. This fix is available with APIM 2.6.0 vanilla distribution so whenever you upload a swagger resource to create an API a swagger spec validation will be carried out. This allowMultiple field in parameter object seems to have been removed in swagger 2.0 (it was available with 1.2). Please refer [1] and [2]. So a v 2.0 swagger definition containing this allowMultiple field is an invalid definition. You can verify this using [3]. Thus, you will face the shown error in APIM 2.6.0, if you try to upload a swagger file with allowMultiple filed in a parameter object. In order to fix this issue, you may have to fix your swagger file to comply with swagger definition first. Hope this would help. [1]. https://github.com/OAI/OpenAPI-Specification/blob/master/versions/1.2.md [2]. https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md [3]. http://editor.swagger.io/ Thanks, Sachini On Mon, Jun 3, 2019 at 2:33 PM Bernard Paris wrote: > Hello, > > no answer for this ? > I just tested with wso2am-3.0.0-m33 and got exactly same issue when > trying to load swagger json exported from APIM-2.1. > > > > > Question: how to migrate dats form APIM-2.1 running PostGres to APIM-2.6 > ou APIM-3.0 running mySQL > > Thanks, > Bernard > > > > Le 27 mai 2019 à 17:00, Bernard Paris a > écrit : > > Hi, > > we want to migrate API définition datas from API manager 2.1 to 2.6. Our > API manager 2.1 runs postgres, the new 2.6 runs mysql. > > I tried this of some APIs: get a swagger.json file out of API manager > 2.1 then try to import it into API manager 2.6 under > > I Have an Existing API > Use an existing API's endpoint or the API Swagger definition to create an > API. > > but this fails for each API I tested. > > > > > > So, what's wrong and what am I to do ? isn't this suppose to work ? > If not what is the way to transfer datas to new system (with different > DBM) ? > > Thanks, > Bernard Paris > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Sachini De Silva* Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Microgateway Ballerina Upgrade to 0.980
Hi all, This is to give an update on this task. I fixed the issues reported in github[1] with following fixes. Issue Fix Verify Kubernetes related annotations (https://github.com/wso2/ product-microgateway/issues/195) https://github.com/wso2/product-microgateway/pull/205/files Enable copy file support for Kubernetes deployment (https://github.com/wso2/ product-microgateway/issues/194) https://github.com/wso2/product-microgateway/pull/208/files Configuration to disable SSL hostname verification for Key manager ( https://github.com/wso2/product-microgateway/issues/193) https://github.com/wso2/product-microgateway/pull/209/files <https://github.com/wso2/product-microgateway/pull/209> Default CORS config in toolkit-config.toml is wrong ( https://github.com/wso2/product-microgateway/issues/206) https://github.com/wso2/product-microgateway/pull/207/files Document the usage of cli-config.toml config file (https://github.com/wso2/ product-microgateway/issues/97) https://docs.google.com/document/d/1VUA675FUDsyvmQjnx4aQx14PuXwJO nH5xo6j0p9OQCI/edit [1]. https://github.com/wso2/product-microgateway/issues <https://github.com/wso2/product-microgateway/issues/195> Thanks, Sachini On Mon, Jul 23, 2018 at 9:38 PM, Nuwan Dias wrote: > Let's go through the scenarios on the docs and verify everything. Ex: > changing back-end url and credentials, etc. > > On Mon, Jul 23, 2018 at 7:55 AM Sachini De Silva > wrote: > >> Tested analytics. Will check rate limiting. >> >> On Mon, Jul 23, 2018 at 6:24 PM, Nuwan Dias wrote: >> >>> How about Analytics, Rate Limiting? >>> >>> On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva >>> wrote: >>> >>>> Hi all, >>>> >>>> Adding to the list of tested scenarios, >>>> >>>> 8. Deploy microgateway in kubernetes with a single API and invoke with >>>> JWT token. >>>> 9. Tested same for a group of labeled APIs. >>>> >>>> Thanks, >>>> Sachini >>>> >>>> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda >>>> wrote: >>>> >>>>> Tested 0.980.1 updated microgateway with single API mode for both >>>>> JWT/OAuth token mode in docker and local mode. Didn't noticed any issues >>>>> and its working as expected. If other scenarios also passed i think we can >>>>> go ahead and do release. >>>>> >>>>> Thanks, >>>>> sanjeewa. >>>>> >>>>> On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara < >>>>>> bhath...@wso2.com> wrote: >>>>>> >>>>>>> I think there was an issue with v0.980 and fixed in v0.980.1. Not >>>>>>> sure if it will affect MG. Please check that. >>>>>>> >>>>>> This was a fix related to packerina. However since this is the only >>>>>> change included, IMO we can bump the version and do the release. >>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Bhathiya >>>>>>> >>>>>>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva >>>>>>> wrote: >>>>>>> >>>>>>>> + [dev] >>>>>>>> >>>>>>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva < >>>>>>>> sachi...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> This is to give an update on how API Microgateway ballerina >>>>>>>>> upgrade is going. >>>>>>>>> >>>>>>>>> RajithR came up with https://github.com/wso2/ >>>>>>>>> product-microgateway/pull/202/files which contains the syntax >>>>>>>>> changes to support ballerina 0.980. >>>>>>>>> >>>>>>>>> I have tested API Microgateway with the above change and listed >>>>>>>>> below are the scenarios I tested. >>>>>>>>> >>>>>>>>> 1. Created gateway distribution for a single API and invoked >>>>>>>>> throug
Re: [Dev] API Microgateway Ballerina Upgrade to 0.980
Tested analytics. Will check rate limiting. On Mon, Jul 23, 2018 at 6:24 PM, Nuwan Dias wrote: > How about Analytics, Rate Limiting? > > On Mon, Jul 23, 2018 at 5:44 AM Sachini De Silva > wrote: > >> Hi all, >> >> Adding to the list of tested scenarios, >> >> 8. Deploy microgateway in kubernetes with a single API and invoke with >> JWT token. >> 9. Tested same for a group of labeled APIs. >> >> Thanks, >> Sachini >> >> On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda >> wrote: >> >>> Tested 0.980.1 updated microgateway with single API mode for both >>> JWT/OAuth token mode in docker and local mode. Didn't noticed any issues >>> and its working as expected. If other scenarios also passed i think we can >>> go ahead and do release. >>> >>> Thanks, >>> sanjeewa. >>> >>> On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa >>> wrote: >>> >>>> >>>> >>>> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara >>> > wrote: >>>> >>>>> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure >>>>> if it will affect MG. Please check that. >>>>> >>>> This was a fix related to packerina. However since this is the only >>>> change included, IMO we can bump the version and do the release. >>>> >>>>> >>>>> Thanks, >>>>> Bhathiya >>>>> >>>>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva >>>>> wrote: >>>>> >>>>>> + [dev] >>>>>> >>>>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva >>>>> > wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> This is to give an update on how API Microgateway ballerina upgrade >>>>>>> is going. >>>>>>> >>>>>>> RajithR came up with https://github.com/wso2/ >>>>>>> product-microgateway/pull/202/files which contains the syntax >>>>>>> changes to support ballerina 0.980. >>>>>>> >>>>>>> I have tested API Microgateway with the above change and listed >>>>>>> below are the scenarios I tested. >>>>>>> >>>>>>> 1. Created gateway distribution for a single API and invoked through >>>>>>> JWT and Oauth tokens. >>>>>>> 2. Tested the same for labelled APIs >>>>>>> 3. Tested overriding endpoints using system variables. >>>>>>> 4. Microgateway analytics >>>>>>> 6. Deploy microgateway in docker and invoked API using JWT and >>>>>>> Oauth2. >>>>>>> 7. Deploy a group of labeled APIs in docker. (to verify >>>>>>> https://github.com/wso2/product-microgateway/issues/199 is fixed) >>>>>>> >>>>>>> Thanks, >>>>>>> Sachini >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Sachini De Silva* >>>>>>> Software Engineer - WSO2 >>>>>>> >>>>>>> Email : sachi...@wso2.com >>>>>>> Mobile : +94714765495 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Sachini De Silva* >>>>>> Software Engineer - WSO2 >>>>>> >>>>>> Email : sachi...@wso2.com >>>>>> Mobile : +94714765495 >>>>>> >>>>>> >>>>> >>>>> -- >>>>> *Bhathiya Jayasekara* >>>>> *Associate Technical Lead,* >>>>> *WSO2 inc., http://wso2.com <http://wso2.com>* >>>>> >>>>> *Phone: +94715478185* >>>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >>>>> <http://www.linkedin.com/in/bhathiyaj>* >>>>> *Twitter: https://twitter.com/bhathiyax >>>>> <https://twitter.com/bhathiyax>* >>>>> *Blog: http://movingaheadblog.blogspot.com >>>>> <http://movingaheadblog.blogspot.com/>* >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks and Regards, >>>> >>>> Isuru H. >>>> +94 716 358 048* <http://wso2.com/>* >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> *Sanjeewa Malalgoda* >>> WSO2 Inc. >>> Mobile : +94 712933253 >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda. >>> blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/> >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Sachini De Silva* >> Software Engineer - WSO2 >> >> Email : sachi...@wso2.com >> Mobile : +94714765495 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > Nuwan Dias > > Director - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- *Sachini De Silva* Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Microgateway Ballerina Upgrade to 0.980
Hi all, Adding to the list of tested scenarios, 8. Deploy microgateway in kubernetes with a single API and invoke with JWT token. 9. Tested same for a group of labeled APIs. Thanks, Sachini On Mon, Jul 23, 2018 at 5:10 PM, Sanjeewa Malalgoda wrote: > Tested 0.980.1 updated microgateway with single API mode for both > JWT/OAuth token mode in docker and local mode. Didn't noticed any issues > and its working as expected. If other scenarios also passed i think we can > go ahead and do release. > > Thanks, > sanjeewa. > > On Mon, Jul 23, 2018 at 1:43 PM Isuru Haththotuwa wrote: > >> >> >> On Mon, Jul 23, 2018 at 1:36 PM, Bhathiya Jayasekara >> wrote: >> >>> I think there was an issue with v0.980 and fixed in v0.980.1. Not sure >>> if it will affect MG. Please check that. >>> >> This was a fix related to packerina. However since this is the only >> change included, IMO we can bump the version and do the release. >> >>> >>> Thanks, >>> Bhathiya >>> >>> On Mon, Jul 23, 2018 at 12:47 PM Sachini De Silva >>> wrote: >>> >>>> + [dev] >>>> >>>> On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> This is to give an update on how API Microgateway ballerina upgrade is >>>>> going. >>>>> >>>>> RajithR came up with https://github.com/wso2/ >>>>> product-microgateway/pull/202/files which contains the syntax changes >>>>> to support ballerina 0.980. >>>>> >>>>> I have tested API Microgateway with the above change and listed below >>>>> are the scenarios I tested. >>>>> >>>>> 1. Created gateway distribution for a single API and invoked through >>>>> JWT and Oauth tokens. >>>>> 2. Tested the same for labelled APIs >>>>> 3. Tested overriding endpoints using system variables. >>>>> 4. Microgateway analytics >>>>> 6. Deploy microgateway in docker and invoked API using JWT and Oauth2. >>>>> 7. Deploy a group of labeled APIs in docker. (to verify >>>>> https://github.com/wso2/product-microgateway/issues/199 is fixed) >>>>> >>>>> Thanks, >>>>> Sachini >>>>> >>>>> -- >>>>> >>>>> *Sachini De Silva* >>>>> Software Engineer - WSO2 >>>>> >>>>> Email : sachi...@wso2.com >>>>> Mobile : +94714765495 >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Sachini De Silva* >>>> Software Engineer - WSO2 >>>> >>>> Email : sachi...@wso2.com >>>> Mobile : +94714765495 >>>> >>>> >>> >>> -- >>> *Bhathiya Jayasekara* >>> *Associate Technical Lead,* >>> *WSO2 inc., http://wso2.com <http://wso2.com>* >>> >>> *Phone: +94715478185* >>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj >>> <http://www.linkedin.com/in/bhathiyaj>* >>> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* >>> *Blog: http://movingaheadblog.blogspot.com >>> <http://movingaheadblog.blogspot.com/>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94 712933253 > > <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda. > blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/> > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sachini De Silva* Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Microgateway Ballerina Upgrade to 0.980
+ [dev] On Mon, Jul 23, 2018 at 12:12 PM, Sachini De Silva wrote: > Hi all, > > This is to give an update on how API Microgateway ballerina upgrade is > going. > > RajithR came up with https://github.com/wso2/ > product-microgateway/pull/202/files which contains the syntax changes to > support ballerina 0.980. > > I have tested API Microgateway with the above change and listed below are > the scenarios I tested. > > 1. Created gateway distribution for a single API and invoked through JWT > and Oauth tokens. > 2. Tested the same for labelled APIs > 3. Tested overriding endpoints using system variables. > 4. Microgateway analytics > 6. Deploy microgateway in docker and invoked API using JWT and Oauth2. > 7. Deploy a group of labeled APIs in docker. (to verify > https://github.com/wso2/product-microgateway/issues/199 is fixed) > > Thanks, > Sachini > > -- > > *Sachini De Silva* > Software Engineer - WSO2 > > Email : sachi...@wso2.com > Mobile : +94714765495 > > -- *Sachini De Silva* Software Engineer - WSO2 Email : sachi...@wso2.com Mobile : +94714765495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
