[Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi IAM Team, I need to create a JDBC secondary user store via admin services and I configured only the mandatory parameters and sent the request. The request was successful and the user store was created. However, when I tried to add a user to that user store, it says the password length is invali

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Dilini, I think it makes sense to populate additional parameters in UI when adding user store from the management console. Yeah, when adding user store via admin services its bit hard to add those number of optional parameters. So I propose following solutions. 1. Improve our documentation and

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Thanks for the reply Godwin. Please see my comments inline. On Wed, Dec 20, 2017 at 5:27 PM, Godwin Shrimal wrote: > Hi Dilini, > > I think it makes sense to populate additional parameters in UI when adding > user store from the management console. > Yes, this is handled correctly from the mana

[Dev] [EI] Average response time for back-end call

Hi Devs, I have a proxy service which calls DSS service. I want to check the average response time of the DSS call in a load test. Do we have a way to check the average response time of the backend call? Thanks Godwin -- *Godwin Amila Shrimal* Associate Technical Lead WSO2 Inc.; http://wso2.com

Re: [Dev] [EI] Average response time for back-end call

Hi Godwin. You can use the JMX monitoring for this. Refer [1]. [1] - https://docs.wso2.com/display/ESB500/JMX+Monitoring Thanks, Vinod On Wed, Dec 20, 2017 at 7:35 PM, Godwin Shrimal wrote: > Hi Devs, > > I have a proxy service which calls DSS service. I want to check the > average response ti

Re: [Dev] [EI] Average response time for back-end call

Thanks for response Vinod, Yes. This is what I wanted. Thanks Godwin On Wed, Dec 20, 2017 at 7:41 PM, Vinod Kavinda wrote: > Hi Godwin. > You can use the JMX monitoring for this. Refer [1]. > > [1] - https://docs.wso2.com/display/ESB500/JMX+Monitoring > > Thanks, > Vinod > > On Wed, Dec 20, 201

Re: [Dev] [EI] Average response time for back-end call

There are two other parameters missing in the docs AIR, that are required for mediation level stats. Refer [2] for them :) [2] - http://soatechflicks.blogspot.com/2017/06/wso2-esb-ei-mediation-latencies-with.html Regards, Vinod On Wed, Dec 20, 2017 at 7:46 PM, Godwin Shrimal wrote: > Thanks fo

Re: [Dev] [EI] Average response time for back-end call

Adding doc team members. Can you please fix the gaps in the documentation ? Thanks Godwin On Wed, Dec 20, 2017 at 7:49 PM, Vinod Kavinda wrote: > There are two other parameters missing in the docs AIR, that are required > for mediation level stats. Refer [2] for them :) > > [2] - http://soa

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Dilini, Please see my comments. I think it makes sense to populate additional parameters in UI when adding > user store from the management console. > Yes, this is handled correctly from the management console side as expected. > > >> Yeah, when adding user store via admin services its bit har

[Dev] Clarification on Federated Authenticators - Client IDs and Client Secrets

Hi All, When configuring external IDPs through connectors, we have client secret and client ID. Some connectors like Facebook, Pinterest allows space character in the client ID and service provider login is successful. Basecamp, Google, LinkedIn, MailChimp and etc connectors do not allow spaces i

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Godwin, Please see my comments inline. On Wed, Dec 20, 2017 at 7:59 PM, Godwin Shrimal wrote: > Hi Dilini, > > Please see my comments. > > I think it makes sense to populate additional parameters in UI when adding >> user store from the management console. >> > Yes, this is handled correctly

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Dilini, Please see my comments. I think it makes sense to populate additional parameters in UI when adding >>> user store from the management console. >>> >> Yes, this is handled correctly from the management console side as >>> expected. >>> >>> Yeah, when adding user store via admin se

Re: [Dev] Clarification on Federated Authenticators - Client IDs and Client Secrets

Hi Isuru, AFAIK we don't want to allow spaces for ClientID and Secret since OAuth ClientID and Secret cannot have spaces. @Fara: Please confirm. Thanks Godwin On Wed, Dec 20, 2017 at 8:29 PM, Isuru Uyanage wrote: > Hi All, > > When configuring external IDPs through connectors, we have client

Re: [Dev] Clarification on Federated Authenticators - Client IDs and Client Secrets

OAuth spec's section [1] doesn't mention the rules on how to generate the client ID and secret values. What it says is the values should be URL encoded. In that case, if it has spaces, those would be converted to %20 and replaced the spaces, which should be OK. So, IMO it's totally up to the devel

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Dilini, After adding the secondary userstore, you can find the config file related to that in *repository/deployment/server/userstores/* location. Although you have not added the regex parameters when you created the userstore from the admin service, I believe it should have added some default

Re: [Dev] [IAM] User store does not behave as expected when it is created through admin services with only mandatory parameters

Hi Tharindu/Godwin, I already checked the config file. The default regex were not added. Following are the only configs available in the file (which are the ones I configured). jdbc:mysql://localhost:3306/is520user wso2carbon A1yNIeGmb1QZHDIk09yOyx/+PWDPNRfOk6tCiCnQWzhFiXFaVu5d

Re: [Dev] Clarification on Federated Authenticators - Client IDs and Client Secrets

Hi Godwin/ Tharindu, Thank you for the explanation. Regards, Isuru *Thanks and Best Regards,* *Isuru Uyanage* *Software Engineer - QA | WSO2* *Mobile : **+94 77 <+94%2077%20767%201807> 55 30752* *LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/

Re: [Dev] [EI] Average response time for back-end call

Created a doc jira [1]. Thanks for reporting! [1] https://wso2.org/jira/browse/DOCUMENTATION-7502 On Wed, Dec 20, 2017 at 7:52 PM, Godwin Shrimal wrote: > Adding doc team members. > > Can you please fix the gaps in the documentation ? > > > Thanks > Godwin > > > > On Wed, Dec 20, 2017 at 7:49 P

[Dev] [ALLDOCS] [CARBON] Do we really need to document 'changing to Embedded H2'?

Hi Jayanga/Johann/Niranjan/Kishanthan/Nilmini, Currently in [1] we give instructions on how to change the carbon database (the H2) to a different database like mysql, mssql etc. In any document where we link off to this doc [1], we usually mention that Embedded H2 is *not* recommended in producti

[Dev] [VOTE] Release WSO2 Stream Processor 4.0.0 RC1

Hi Devs, We are pleased to announce the release candidate of WSO2 Stream Processor 4.0.0. This is the Release Candidate version 1 of the WSO2 Stream Processor 4.0.0 Please download, test the product and vote. Vote will be open for 72 hours or as needed. Known issues: https://github.com/wso2/pro