Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

Cool, thanks for checking this. If the /oauth2 webapp is going to be used for scope registrations, then we better make its URL obvious that its dealing with scopes and doesn't have anything to do with dcr stuff. On Fri, Sep 15, 2017 at 10:04 AM, Harsha Thirimanna wrote: > On

Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

On Fri, Sep 15, 2017 at 9:45 AM, Nuwan Dias wrote: > Hi Ishara, > > Thanks for the confirmation. > > There are two DCR webapps within IS 5.4.0 alpha2, one which goes as > ​​ > /api/identity/*oauth*/dcr/v1.0 and the other which goes as > ​​ > /api/identity/*oauth2*/dcr/v1.0.

Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

Hi Ishara, Thanks for the confirmation. There are two DCR webapps within IS 5.4.0 alpha2, one which goes as /api/identity/*oauth*/dcr/v1.0 and the other which goes as /api/identity/ *oauth2*/dcr/v1.0. According to the basepath in the Swagger doc, the second app should be the correct one. But

Re: [Dev] Multiple scopes for REST resources in APIM Store and Publisher

We created a github issue to track this https://github.com/wso2/product-apim/issues/1579. On Fri, Sep 15, 2017 at 2:11 AM, Youcef HILEM wrote: > Hi All, > > +1 for this capability. > > Yes needs have been expressed and questions are being asked about the > current

Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

HI Nuwan, On Fri, Sep 15, 2017 at 7:14 AM, Nuwan Dias wrote: > Hi Hasintha, > > Isn't this the old DCR implementation? This one doesn't mention about > DCRM. Where can I get information on using DCRM? > > I was under the impression the new DCR implementation was documented at >

Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

Hi Hasintha, Isn't this the old DCR implementation? This one doesn't mention about DCRM. Where can I get information on using DCRM? I was under the impression the new DCR implementation was documented at [3]. This doc mentions about DCRM too, hence why I thought that should be the new

Re: [Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

For IS endpoint should be https://localhost:9443/identity/connect/register. Refer [1]​[2] [1] http://openid.net/specs/openid-connect-registration-1_0.html [2] https://docs.wso2.com/display/IS540/OpenID+Connect+Dynamic+Client+Registration ___ Dev mailing

Re: [Dev] Multiple scopes for REST resources in APIM Store and Publisher

Hi All, +1 for this capability. Yes needs have been expressed and questions are being asked about the current limitation. Thanks, Youcef HILEM -- Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html ___ Dev mailing list

Re: [Dev] How to update subscription tier

Hi Vazquez, Currently, it's not possible to do it via UI. You will either need to resubscribe or use AM_SUBSCRIPTION table to achieve it. Thanks, Harsha On Fri, Sep 15, 2017 at 12:23 AM, Vazquez-Hidalgo, Javier < javier.vazquez-hida...@tdsecurities.com> wrote: > Hello, > > > > Is it possible

[Dev] How to update subscription tier

Hello, Is it possible to have a super user (Admin) that can change subscription tiers to other users, let's say I want to upgrade a user subscription from Bronze to Unlimited?, I couldn't find a way to do it from publisher nor admin sites. Regards, Javier If you wish to unsubscribe from

[Dev] Have we tested the new DCR on IS 5.4.0 Alpha2?

Hi, Have we tested the new DCR endpoints on IS 5.4.0 Alpha2? I have tried making the following request but it returns a 200 with the html content of the carbon login page. There aren't any error logs as well. POST https://localhost:9443/api/identity/oauth2/dcr/v1.0/register Headers:

Re: [Dev] Multiple scopes for REST resources in APIM Store and Publisher

On Thu, Sep 14, 2017 at 5:18 PM, Viduranga Gunarathne wrote: > Hi, > With the existing implementation in the store and publisher yaml, there is > only a single scope provided in the security for resources as shown in > Image #1. But other swagger definitions tend to have

Re: [Dev] Datasource support in secondary user stores

On Thu, Sep 14, 2017 at 10:41 PM, Omindu Rathnaweera wrote: > And one more thing, shall we also change the default values for maxIdle > and maxActive to avoid getting the following WARN ? > > *WARN {org.apache.tomcat.jdbc.pool.ConnectionPool} - maxIdle is larger > than

Re: [Dev] Datasource support in secondary user stores

And one more thing, shall we also change the default values for maxIdle and maxActive to avoid getting the following WARN ? *WARN {org.apache.tomcat.jdbc.pool.ConnectionPool} - maxIdle is larger than maxActive, setting maxIdle to: 40* On Thu, Sep 14, 2017 at 10:33 PM, Omindu Rathnaweera

Re: [Dev] Datasource support in secondary user stores

Following are the pooling properties we support for JDBC user stores ATM as per [1]. maxActive minIdle maxIdle maxWait testWhileIdle timeBetweenEvictionRunsMillis minEvictableIdleTimeMillis validationQuery +1 for adding the rest of the properties. We can use [2] as a reference for the rest of

Re: [Dev] Multiple scopes for REST resources in APIM Store and Publisher

Although we don't have a requirement to attach multiple scopes for a given resource, it may come up as a need in the future. So if possible let's not try to make any assumptions based on the current situation. On Thu, Sep 14, 2017 at 5:18 PM, Viduranga Gunarathne wrote: >

Re: [Dev] SCIM 2.0 as default in IS 5.4.0

What do you mean by default...? Don't have the API versioned...? Thanks & regards, -Prabath On Mon, Sep 11, 2017 at 5:04 AM, Pulasthi Mahawithana wrote: > Hi, > > Shall we make $subject instead of SCIM 1.1? Any known issues on having it > as default? Users who are migrating

Re: [Dev] Please review and merge PR for kernel

@thusitha: since the PR is sent to the 4.4.x branch, it will not close the issue when the PR is merged. Therefore we will have to close the issue after merging the PR. Regards, Nira On Thu, Sep 14, 2017 at 11:28 AM, Thusitha Thilina Dayaratne < thusit...@wso2.com> wrote: > Hi Pulasthi, > > PR

Re: [Dev] Please review and merge PR for kernel

Hi Pulasthi, PR merged. Thanks Thusitha On Thu, Sep 14, 2017 at 6:51 PM, Pulasthi Mahawithana wrote: > Hi, > > Please review and merge [1], which fixes [2]. Related Identity JIRA is at > [3]. > > [1] https://github.com/wso2/carbon-kernel/pull/1527 >

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

Thanks for the information Vijitha. Thanks, Chamalee On Thu, Sep 14, 2017 at 5:28 PM, Vijitha Ekanayake wrote: > Hi Chamalee, > > This feature has been implemented after the ESB 500 release and it should > be available in EI. > You need to add following processors

[Dev] Please review and merge PR for kernel

Hi, Please review and merge [1], which fixes [2]. Related Identity JIRA is at [3]. [1] https://github.com/wso2/carbon-kernel/pull/1527 [2]

Re: [Dev] Please review and merge the PR

Hi Sathya, Your PR was merged to carbon-deployment 4.7.x. Thanks, Dilan. *Dilan U. Ariyaratne* Senior Software Engineer WSO2 Inc. Mobile: +94766405580 <%2B94766405580> lean . enterprise . middleware On Thu, Sep 14, 2017 at 5:39 AM, Dilan Udara Ariyaratne

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

Hi Chamalee, This feature has been implemented after the ESB 500 release and it should be available in EI. You need to add following processors under HttpGetRequestProcessors in carbon.xml to get feature to work. swagger.json org.wso2.carbon.

[Dev] Multiple scopes for REST resources in APIM Store and Publisher

Hi, With the existing implementation in the store and publisher yaml, there is only a single scope provided in the security for resources as shown in Image #1. But other swagger definitions tend to have multiple scopes for a single resource as shown in Image #2. Currently there is no requirement

Re: [Dev] [Integration Cloud] Swagger Support for ESB REST APIs

Hi Maheeka and ESB team, Is $Subject available in ESB 5.0.0 ? Do we have any documentation on $Subject that we can use to try swagger support on ESB REST APIs ? I found mail thread [1] and JIRA [2] related to this. Appreciate your help. [1] Integration Cloud - ESB on Cloud [2]