Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Ashen Weerathunga]

Hi,

Tested the following IS Analytics features with IS Runtime,

   - Login attempts analytics
   - Login session analytics
   - Suspicious login alerts
   - Customizing alerts using template manager

[+] Stable - go ahead and release

Thanks,
Ashen

On Mon, Jan 9, 2017 at 11:51 AM, Thanuja Jayasinghe 
wrote:

> Hi,
>
> Tested following,
>
>- Account recovery with notification
>- Account recovery with security questions
>- Recaptcha
>- Self signup
>
> [+] Stable - go ahead and release
>
> Thanks,
> Thanuja
>
> On Mon, Jan 9, 2017 at 11:05 AM, Rushmin Fernando 
> wrote:
>
>> Tested following features with MSSQL
>>
>> 1) SAML flow
>> 2) OAuth
>> 3) OIDC
>> 4) SAML metedata profile
>>
>>   [+] Stable - go ahead and release
>>
>> Best Regards
>> Rushmin
>>
>> On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:
>>
>>> Hi,
>>> I tested the following on the Identity Server 5.3.0-RC3 pack,
>>>
>>>- Discovery
>>>- DCR
>>>- Form Post
>>>- Introspection
>>>- SCIM API
>>>- User Management
>>>
>>> Worked fine without any issues.
>>> [+] Stable - go ahead and release
>>>
>>> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana <
>>> pulast...@wso2.com> wrote:
>>>
 Hi All,

 This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.

 This release fixes the following issues:

 Runtime : https://wso2.org/jira/issues/?filter=13612
 Analytics : https://wso2.org/jira/issues/?filter=13614

 Source and distribution

 Run-time : https://github.com/wso2/prod
 uct-is/releases/tag/v5.3.0-rc3
 Analytics : https://github.com/wso2/anal
 ytics-is/releases/tag/v5.3.0-rc3

 Please vote as follows.
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 Thanks,
 - WSO2 Identity Server Team -

 --
 *Pulasthi Mahawithana*
 Senior Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022 <+94%2071%20517%209022>
 Blog: http://blog.pulasthi.org

 

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Dinali Rosemin Dabarera*
>>> Software Engineer
>>> WSO2 Lanka (pvt) Ltd.
>>> Web: http://wso2.com/
>>> Email : gdrdabar...@gmail.com
>>> LinkedIn 
>>> Mobile: +94770198933 <+94%2077%20019%208933>
>>>
>>>
>>>
>>>
>>> 
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Best Regards*
>>
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> mobile : +94775615183
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanuja Lakmal*
> Senior Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891 +94758009992
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: tel:94716042995 <94716042995>
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [C5] Usage of kernel-version.txt in C5

[Jayanga Dissanayake]

Hi All,

IMO, there is no point having a separate file just to print the kernel
version. I think we could derive the version from carbon.core bundle if we
need the -version option.

The placeholders in the kernel-version.txt file are updated with the
corresponding values given in the filter.properties file at compile time.
Hence all the product teams will have to provide valid values for the
placeholders in kernel-version.txt on the product specific filter.properties
file. Otherwise, the file kernel-version.txt will not get updated properly.

One other concern is, with the C4 based patch model we packed a  separate
*.txt file with the carbon version and patch number. But with C5 and its
update model (yet to be discussed), I think we need to support "-version"
without having a separate file.

Thanks,
Jayanga.


*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259


On Mon, Jan 9, 2017 at 11:22 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Folks,
>
> I am referring to carbon-kernel git issue 1239 -
> https://github.com/wso2/carbon-kernel/issues/1239
>
> When I looked into the usage of this file, the only usage found is getting
> the kernel version from that file and
> printing it on the console when command ./carbon.sh version is invoked.
>
> AFAIU, there are two concerns that we need to consider here.
>
> [1] Do we really need this version option with ./carbon.sh command ?
>  My opinion is that it's a nice to have feature with respect to user
> experience.
>  Nowadays, many of the softwares support this handy feature with
> -version option preceded by some alias to represent the corresponding
> software.
>  For ex:
>  Java and mvn have following outputs for -version option
>
>  command :
>  java -version
>  output :
>  Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
>  Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
>
>  command :
>  mvn -version
>  output :
>  Apache Maven 3.3.9
>  Maven home: /usr/share/maven
>  Java version: 1.8.0_102, vendor: Oracle Corporation
>  Java home: /home/abc/Programs/Java/jdk1.8.0_102/jre
>  Default locale: en_US, platform encoding: UTF-8
>  OS name: "linux", version: "4.4.0-57-generic", arch: "amd64", family:
> "unix"
>
> [2] If we are supporting this option with ./carbon.sh, what is the ideal
> way to obtain any version information ?
>  Currently, we are getting the version value of carbon kernel with the
> aforementioned kernel-version.txt file which resides in /bin.
>  For ex:
>
>  command :
>  ./carbon.sh version
>  output :
>  WSO2 Carbon Kernel v5.2.0-SNAPSHOT
>
>  So, the question would be that "Is this the ideal way of doing this"
> or will there be any other better alternatives ?
>
> Please share your valuable thoughts on this.
>
> Cheers,
> Dilan.
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> ___
> 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

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC1

[Ayoma Wijethunga]

[-] Broken - do not release (Due to a security related issue identified)

Thank you,
Ayoma.

On Sat, Jan 7, 2017 at 5:16 PM, Prakhash Sivakumar 
wrote:

> Hi all,
>
> Please keep the vote on hold as we are still analyzing security reports
> provided by the team and verifying the previous fixes.
>
> Thanks,
>
> On Fri, Jan 6, 2017 at 10:55 PM, Praminda Jayawardana 
> wrote:
>
>> Hi All,
>>
>> This is the 1st Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/produc
>> t-apim/releases/download/v2.1.0-rc1/wso2am-2.1.0-RC1.zip
>> Analytics : https://github.com/wso2/analyt
>> ics-apim/releases/download/v2.1.0-rc1/wso2am-analytics-2.1.0-RC1.zip
>> Tooling : https://github.com/wso2/devstu
>> dio-tooling-apim/releases/tag/v2.1.0
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Prakhash Sivakumar
> Software Engineer | WSO2 Inc
> Platform Security Team
> Mobile : +94771510080 <+94%2077%20151%200080>
> Blog : https://medium.com/@PrakhashS
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ayoma Wijethunga
Software Engineer
Platform Security Team
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

Mobile : +94 (0) 719428123 <+94+(0)+719428123>
Blog : http://www.ayomaonline.com
LinkedIn: https://www.linkedin.com/in/ayoma
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Thanuja Jayasinghe]

Hi,

Tested following,

   - Account recovery with notification
   - Account recovery with security questions
   - Recaptcha
   - Self signup

[+] Stable - go ahead and release

Thanks,
Thanuja

On Mon, Jan 9, 2017 at 11:05 AM, Rushmin Fernando  wrote:

> Tested following features with MSSQL
>
> 1) SAML flow
> 2) OAuth
> 3) OIDC
> 4) SAML metedata profile
>
>   [+] Stable - go ahead and release
>
> Best Regards
> Rushmin
>
> On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:
>
>> Hi,
>> I tested the following on the Identity Server 5.3.0-RC3 pack,
>>
>>- Discovery
>>- DCR
>>- Form Post
>>- Introspection
>>- SCIM API
>>- User Management
>>
>> Worked fine without any issues.
>> [+] Stable - go ahead and release
>>
>> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana > > wrote:
>>
>>> Hi All,
>>>
>>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> This release fixes the following issues:
>>>
>>> Runtime : https://wso2.org/jira/issues/?filter=13612
>>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>>
>>> Source and distribution
>>>
>>> Run-time : https://github.com/wso2/prod
>>> uct-is/releases/tag/v5.3.0-rc3
>>> Analytics : https://github.com/wso2/anal
>>> ytics-is/releases/tag/v5.3.0-rc3
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 Identity Server Team -
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Senior Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>>> Blog: http://blog.pulasthi.org
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Dinali Rosemin Dabarera*
>> Software Engineer
>> WSO2 Lanka (pvt) Ltd.
>> Web: http://wso2.com/
>> Email : gdrdabar...@gmail.com
>> LinkedIn 
>> Mobile: +94770198933 <+94%2077%20019%208933>
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanuja Lakmal*
Senior Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891 +94758009992
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Supporting MongoDB as a Secondary Userstore : an Extension for WSO2 Platform

[Asantha Thilina]

Hi all,

I am willing to contribute and January (30, 31) is ok for me for a meeting

thanks,
Asantha

On Sun, Jan 8, 2017 at 10:20 PM, Tharindu Edirisinghe 
wrote:

> Hi Devs,
>
> Along with Google Summer of Code 2016, we initiated this project [1] for
> supporting MongoDB as a secondary userstore for WSO2 products.
>
> Asantha (CC'ed) here successfully completed the project where it supported
> IS 5.1.0. (for IS 5.2.0 we need to do some minor modification to get it to
> working and for IS 5.3.0 which is about to be released.. we'll have to do
> some more changes because the claim management API is changed).
>
> We cannot ship this with a WSO2 product, because it is not scalable. The
> end user might use a different version of MongoDB database or JDBC driver,
> releasing patches would be difficult if any bug is found etc.
>
> Therefore the best way is to develop it as a connector (extension) and
> publicly release to WSO2 store.
>
> For that, I am initiating this email where we can discuss on how to
> proceed with this.
>
> @Kathees - I hope you can take the ownership of this. We can get Asantha's
> help as well whenever necessary.
>
> My idea is to have a meeting for this during the last week of January
> (30,31) and come up with a plan.
>
> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+
> 2016#ProjectProposalsfor2016-Proposal21:[IS]DocumentBasedNoSQLSupportforWS
> O2IdentityServerDatabase
>
> Thanks,
> TharinduE
>
> --
>
> Tharindu Edirisinghe
> Senior Software Engineer | WSO2 Inc
> Platform Security Team
> Blog : tharindue.blogspot.com
> mobile : +94 775181586 <+94%2077%20518%201586>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please merge the PR

[Samitha Chathuranga]

Hi,

Can you please review and merge the PR [1].

[1] - https://github.com/wso2/puppet-base/pull/4

Thanks,
Samitha

-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Jayanga Kaushalya]

Tested the OAuth 2 Form Post response mode with an OWIN client in Windows
2012. No issues found.

[+] Stable - Go ahead and release.

Thanks!

*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Supporting MongoDB as a Secondary Userstore : an Extension for WSO2 Platform

[Tharindu Edirisinghe]

Hi Devs,

Along with Google Summer of Code 2016, we initiated this project [1] for
supporting MongoDB as a secondary userstore for WSO2 products.

Asantha (CC'ed) here successfully completed the project where it supported
IS 5.1.0. (for IS 5.2.0 we need to do some minor modification to get it to
working and for IS 5.3.0 which is about to be released.. we'll have to do
some more changes because the claim management API is changed).

We cannot ship this with a WSO2 product, because it is not scalable. The
end user might use a different version of MongoDB database or JDBC driver,
releasing patches would be difficult if any bug is found etc.

Therefore the best way is to develop it as a connector (extension) and
publicly release to WSO2 store.

For that, I am initiating this email where we can discuss on how to proceed
with this.

@Kathees - I hope you can take the ownership of this. We can get Asantha's
help as well whenever necessary.

My idea is to have a meeting for this during the last week of January
(30,31) and come up with a plan.

[1]
https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal21:[IS]DocumentBasedNoSQLSupportforWSO2IdentityServerDatabase

Thanks,
TharinduE

-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Maduranga Siriwardena]

Tested the following on the Identity Server 5.3.0-RC3 pack,

   - Workflow related features
   - JIT provisioning
   - Facebook federated authenticator
   - Google federated authenticator
   - Authorization for service providers
   - Federated user account association

 [+] Stable - go ahead and release

On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc; http://wso2.com/

Email: madura...@wso2.com
Mobile: +94718990591
Blog: http://madurangasblogs.blogspot.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Rushmin Fernando]

Tested following features with MSSQL

1) SAML flow
2) OAuth
3) OIDC
4) SAML metedata profile

  [+] Stable - go ahead and release

Best Regards
Rushmin

On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

mobile : +94775615183
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Isura Karunaratne]

Hi,

Tested following features

   - Account Recovery- Notification
   - Account Recovery - Security Question one by one
   - Account Recovery - Security Question at once
   - Recaptcha
   - Password History
   - Self Signup
   - Ask Password
   - User Email Verified
   - Password Pattern
   - Account Lock
   - User Mangement functionality
   - Email template internalization
   - Challenge Question internalization
   - HTML based email template.


These scenarios worked as expected.
[+1] Go ahead and release.

Thanks
Isura



*Isura Dilhara Karunaratne*
Senior Software Engineer | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/




On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> 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

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Ishara Karunarathna]

Hi,

Tested,
OAuth Discovery
OAuth DCR
IS Analytics with IS Runtime.

Worked fine without any issues.
[+] Stable - go ahead and release

-Ishara


On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> This release fixes the following issues:
>
> Runtime : https://wso2.org/jira/issues/?filter=13612
> Analytics : https://wso2.org/jira/issues/?filter=13614
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.
> 3.0-rc3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 Identity Server Team -
>
> --
> *Pulasthi Mahawithana*
> Senior Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022 <+94%2071%20517%209022>
> Blog: http://blog.pulasthi.org
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Harsha Thirimanna]

Hi,

Tested Identity Workflow with RC3 pack and worked without having any issues.

[+] Stable - go ahead and release


*Harsha Thirimanna*
*Associate Tech Lead | WSO2*

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122


On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> 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

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Dimuthu De Lanerolle]

I have tested following  ,

 a) Password History Validation
 b) Account Suspension
c) Token Introspection
d) Dynamic Client Registration
e) Discovery
f) User challenge question internationalization

[+] Stable - go ahead and release

Regards

On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Dharshana Warusavitharana]

Hi All,

Tested following areas on  Identity Server 5.3.0-RC3 pack
1. XACML policy deployment and XACML API.
2. Policy based provisioning.
3. Access policies during authorization flow.
4. Sample policies for Provisioning and Authorization.

 [+] Stable - go ahead and release

Thank you,
Dharshana.




On Mon, Jan 9, 2017 at 9:33 AM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Dharshana Warusavitharana
Associate Technical Lead
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Chamila Wijayarathna]

Hi all,

Tested following scenarios on Windows 10.

   - Creating user through management console and self registration
   - Self registration with account lock on creation disabled
   - Tenant wise identity management
   - identity event properties
   - Claim management
   - Account locking
   - Login to dashboard, user profile update, change password, account
   association through dashboard

No blocking issues found
[+] Stable - go ahead and release

On Mon, Jan 9, 2017 at 3:03 PM, Dinali Dabarera  wrote:

> Hi,
> I tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Discovery
>- DCR
>- Form Post
>- Introspection
>- SCIM API
>- User Management
>
> Worked fine without any issues.
> [+] Stable - go ahead and release
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
>> rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chamila Dilshan Wijayarathna,
PhD Research Student
The University of New South Wales (UNSW Canberra)
Australian Centre for Cyber Security
Australian Defence Force Academy
PO Box 7916, Canberra BA ACT 2610
Australia
Mobile:(+61)416895795
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [C5] Usage of kernel-version.txt in C5

[Dilan Udara Ariyaratne]

Hi Folks,

I am referring to carbon-kernel git issue 1239 - https://github.com/wso2/
carbon-kernel/issues/1239

When I looked into the usage of this file, the only usage found is getting
the kernel version from that file and
printing it on the console when command ./carbon.sh version is invoked.

AFAIU, there are two concerns that we need to consider here.

[1] Do we really need this version option with ./carbon.sh command ?
 My opinion is that it's a nice to have feature with respect to user
experience.
 Nowadays, many of the softwares support this handy feature with
-version option preceded by some alias to represent the corresponding
software.
 For ex:
 Java and mvn have following outputs for -version option

 command :
 java -version
 output :
 Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
 Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)

 command :
 mvn -version
 output :
 Apache Maven 3.3.9
 Maven home: /usr/share/maven
 Java version: 1.8.0_102, vendor: Oracle Corporation
 Java home: /home/abc/Programs/Java/jdk1.8.0_102/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: "linux", version: "4.4.0-57-generic", arch: "amd64", family:
"unix"

[2] If we are supporting this option with ./carbon.sh, what is the ideal
way to obtain any version information ?
 Currently, we are getting the version value of carbon kernel with the
aforementioned kernel-version.txt file which resides in /bin.
 For ex:

 command :
 ./carbon.sh version
 output :
 WSO2 Carbon Kernel v5.2.0-SNAPSHOT

 So, the question would be that "Is this the ideal way of doing this"
or will there be any other better alternatives ?

Please share your valuable thoughts on this.

Cheers,
Dilan.

*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [C5] Self sign-up in C5 User Portal

[Indunil Upeksha Rathnayake]

Hi,

I'm having following concerns regarding claim profile, user store domain
and credentials with related to self sign-up.

*1) Selecting a claim profile for loading claims related to user self
sign-up*

   - Use default claim-profile
   - Only a single profile called "self sign-up"
   - There can be several claim profiles based on the service provider/user
   store domain
   - Have a default claim profile for self sign-up as "self-signUp-default"
   and for each service provider we can define claim profiles with the prefix
   "self-signUp" (ex: "self-signUp-serviceProvider1").

*2) User store domain where users getting added in self sign-up*

   - In the UI, it's not appropriate to expose all the user store domains
   which supports self sign-up, so that user has to added the user name with
   the user store domain (ex: "US1/user1")
   - Admin has to configure the user store domains that supports self
   sign-Up. And in each SP, can configuration where the users getting added.

*3) Suitable field in UI to add credentials*

   - There can be multiple options for adding credentials, all should be
   included in the UI by default.
   - Configure Credential profiles for self sign-up etc.

Appreciate your ideas on selecting appropriate ways of handling above
mentioned scenarios.

Thanks and Regards

On Sun, Jan 8, 2017 at 11:20 AM, Gayan Gunawardana  wrote:

>
>
> On Fri, Jan 6, 2017 at 5:12 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> Thanks for all of your ideas and suggestions. As I have mentioned,
>> currently for M1, we are planning to cover user self sign-up without any
>> email notification(user will be registered and automatically get logged
>> in).  But I think, including your ideas following things would be good
>> improvements to have in future releases.
>>
>> *1)  Configurable option to enable/disable email confirmation*
>>
>>- Admin should be having flexibility to configure self sign-up with
>>email verification and uncontrolled sign up for user store domains
>>
>> *2)  Self sign-up configured in user store level*
>>
>>- Allow anyone to sign up(no restrictions) or restrict users to
>>specific domains
>>- Should be able to configure a particular user store where self sign
>>up users should go, since there can be multiple user store domains and 
>> some
>>are read only etc
>>
>>  As I understood both of above configurations are user store level
> configurations. In user store level there should be a configurations to say
> Enable/Disable self sign-up. If self sign-up enabled then next
> configuration is to enable email verification or uncontrolled sign up.
> Also does end-user need to know user store domain they are going to
> sign-up or all self sign-up users are gone to single user store based on
> admin configuration ?
>
>> *3) Administrators should receive en email when a new account is created*
>>
>> Need to discuss further about these and make user stories if needed.
>>
>> Thanks and Regards
>>
>> On Fri, Jan 6, 2017 at 5:08 PM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Thanks for your reply. For M1, we are planning to cover user self
>>> sign-up without any email notification(user will be registered and
>>> automatically get logged in). For future releases captcha should be
>>> included and that need to be covered in the user stories.
>>>
>>> Thanks and Regards
>>>
>>> On Wed, Jan 4, 2017 at 9:41 AM, Nuwan Dias  wrote:
>>>
 Having a captcha should be supported OOTB in the default portal. I
 assume we've considered that to be so in C5?

 On Wed, Jan 4, 2017 at 9:22 AM, Dimuthu Leelarathne 
 wrote:

>
>
> On Tue, Jan 3, 2017 at 1:00 PM, Ishara Karunarathna 
> wrote:
>
>>
>>
>> On Tue, Jan 3, 2017 at 12:52 PM, Johann Nallathamby 
>> wrote:
>>
>>> What are the new user stories we are trying to implement that are
>>> not already there in IS 5.3.0? Can we come up with a list of new
>>> requirements? Isn't most of the above user stories already there in IS
>>> 5.3.0?
>>>
>> Yes in 5.3.0 we have almost complete user store. But when it comes to
>> C5 implementation we can't cover it with a single milestone release,So we
>> need to start with a simple user story and use different version of that
>> adding other use cases associated with that.
>>
>>
> First we need to envision what we are going to achieve in the long
> run. Then we need to start with the simplest case. For C5 are we trying to
> achieve something different to what we already have?
>
> thanks,
> Dimuthu
>
> -Ishara
>>
>>
>>> On Tue, Jan 3, 2017 at 10:30 AM, Ishara Karunarathna <
>>> isha...@wso2.com> wrote:
>>>
 Hi Indunil,

 When we think about self sign up.
 basic 

Re: [Dev] C5 Carbon JNDI implementation does not support for LDAP

[Ishara Karunarathna]

Hi Kishanthan,

I have added support to load built in JRE providers[1]. Since JRE already
has LDAP provider we can use this.

-Ishara
[1] https://github.com/wso2/carbon-jndi/pull/32



On Wed, Jan 4, 2017 at 4:37 PM, Kishanthan Thangarajah 
wrote:

>
>
> On Tue, Jan 3, 2017 at 11:24 AM, Ishara Karunarathna 
> wrote:
>
>> Hi Kernel team,
>>
>> Current carbon JNDI Implementation does not support for LDAPs. Basically
>> it does not support for
>> DirContext operations.
>>
>
> We did not have a requirement to support this that is why it is not
> implemented. Since IS will mostly be using LDAP related JNDI lookups and it
> should be supported with the provider implementation (may be apache
> directory and need to check whether this would work with jre supported
> providers), it is best that if you guys can work on it and add to
> carbon-jndi?
>
>
>
>> In addition to that it need to support to load JRE supported context
>> providers.
>>
>> To implement LDAP connector for User management core in C5 base IS we
>> need this.
>> Can we get improvement  ?
>>
>> Thanks,
>> Ishara
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <+94%2071%20799%206791>
>>
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635 <+94%2077%20342%206635>
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Ishara Karunarathna
Associate Technical Lead
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
+94717996791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Dinali Dabarera]

Hi,
I tested the following on the Identity Server 5.3.0-RC3 pack,

   - Discovery
   - DCR
   - Form Post
   - Introspection
   - SCIM API
   - User Management

Worked fine without any issues.
[+] Stable - go ahead and release

On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> This release fixes the following issues:
>
> Runtime : https://wso2.org/jira/issues/?filter=13612
> Analytics : https://wso2.org/jira/issues/?filter=13614
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.
> 3.0-rc3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 Identity Server Team -
>
> --
> *Pulasthi Mahawithana*
> Senior Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022 <+94%2071%20517%209022>
> Blog: http://blog.pulasthi.org
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933





___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Ayesha Dissanayaka]

Hi team,

I have tested below scenarios in super tenant and tenant mode both as non
email and email as username.


   1.

   Account Management
   1.

  User Self Registration
  1.

 Self signup with email confirmation
 2.

 Self signup without email confirmation
 3.

 reCaptcha validation at self signup
 2.

  Account Recovery
  1.

 Username Recovery
 2.

 Password Recover
 -

Notification Based Password Recovery
-

Challenge Question Based Password Recovery
1.

   Recover with Secret Questions sequentially
   2.

   Challenge Question Internationalization
   3.

   reCaptcha validation at password recovery
   -

Email Notification in Password recovery flow
1.

   When starting password recovery flow
   2.

   After successful completion of password recovery
   -

Block brute force attacks on password reset
3.

  Password Reset
  1.

 Recovery Email with a link to reset password
 2.

 Recovery Email with a OTP
 3.

 Offline OTP
 2.

   Password History validation
   3.

   Login Management
   1.

  reCaptcha for SSO Login
  2.

  Account Locking at failed attempts and increase lock time-out
  exponentially
  3.

  Resending Email verification code
  4.

   Email Configuration
   1. *Email template internationalization*
   5. Federation - Oauth/OIDC
  1. SAML to Oauth
  2. OIDC to Oauth
  3. PassiveSTS to Oauth
  4. Claim Mappings
  5. JIT Provisioning
  6. Outbound Provisioning with JIT
  7. Account Association and claims


Those scenarios worked as expected.
[+1] Go ahead and release.

Thanks!
-Ayesha

On Mon, Jan 9, 2017 at 6:53 AM, Kasun Bandara  wrote:

> Hi IS team,
>
> Tested the following on the Identity Server 5.3.0-RC3 pack,
>
>
>- Email Internationalisation Feature (Tenant wise support)
>   - Email Templates type addition
>   - Email Templates addition
>   - Update and Delete Email templates
>- HTML support for email template management (Tenant wise support))
>
> [+] Stable - go ahead and release
>
> Regards.
> Kasun
>
> Kasun Gayan Bandara
> PhD Research Student
> Machine Learning Group
>
> Faculty of Information Technology, Clayton
> Monash University
> 25 Exhibition Walk, Clayton Campus
> Wellington Road
> Clayton VIC 3800
> Australia.
>
> E: herath.band...@monash.edu
> M (+61) 43 491 6476
>
> 
>
>
>
> On Mon, Jan 9, 2017 at 6:05 AM, Farasath Ahamed 
> wrote:
>
>> Tested the following on the Identity Server 5.3.0-RC3 pack,
>>
>>- Create Service Provider by importing SAML metadata file.
>>- Export Resident IDP metadata.
>>- SAML SSO for apps hosted on Apache2 using mod_auth_mellon with
>>Identity Server.
>>- Verify CSRF protection for dashboard apps.
>>- Verify IDENTITY- 
>>- Verify IDENTITY-5563 
>>- Recover Password with user locale based challenge questions.
>>- Add User account association between two local user accounts.
>>
>>  [+] Stable - go ahead and release
>>
>>
>> Thanks,
>> Farasath Ahamed
>> Software Engineer, WSO2 Inc.; http://wso2.com
>> Mobile: +94777603866
>> Blog: blog.farazath.com
>> Twitter: @farazath619 
>> 
>>
>>
>>
>> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana > > wrote:
>>
>>> Hi All,
>>>
>>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> This release fixes the following issues:
>>>
>>> Runtime : https://wso2.org/jira/issues/?filter=13612
>>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>>
>>> Source and distribution
>>>
>>> Run-time : https://github.com/wso2/prod
>>> uct-is/releases/tag/v5.3.0-rc3
>>> Analytics : https://github.com/wso2/anal
>>> ytics-is/releases/tag/v5.3.0-rc3
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 Identity Server Team -
>>>
>>> --
>>> *Pulasthi Mahawithana*
>>> Senior Software Engineer
>>> WSO2 Inc., http://wso2.com/
>>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>>> Blog: http://blog.pulasthi.org
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> 

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

[Isuru Haththotuwa]

On Mon, Jan 9, 2017 at 7:54 AM, Isuru Haththotuwa  wrote:

>
>
> On Fri, Jan 6, 2017 at 5:19 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Setting a default value for empty fields being sent seems to be best.
>>
>> Furthermore we can have default values set in our DTO objects in case a
>> given field is omitted altogether.
>>
>> So handling both the above scenarios can overcome the limitation in
>> Oracle.
>>
>> But I dont know if this is good for the REST API user experience, when
>> retrieving data that contains these default values.
>>
> Additionally this could affect the user experience in UIs as well.
>
> How about we just keep a default value to NULL in DB level and then filter
> it from UI? Since anyway Oracle treats zero length String as NULLs, even if
> the user enters an empty String it will then be automatically. The rest API
> will still return the default value if invoked directly though.
>
s/automatically/automatically filtered/g

>
>> On 6 January 2017 at 15:28, Tharindu Dharmarathna 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 6, 2017 at 3:26 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Hi All,

 I faced $Subject in Oracle database while running integration test on
 C5 on top.

 *Observation*

 when insert empty string ("") it was save as null in database.

 While going through SO I had found [1] , which did happen in oracle
 database.


 We have come up with several ways to handle empty strings which user
 sends through the rest api.

 1.  Validate the request and send error when giving empty strings
 2.  Set default value like "N/A" into the fields which send as empty.

 Is there any other way to handle this problem ?.

 [1] - http://stackoverflow.com/questions/13278773/null-vs-empty-
 string-in-oracle

 Thanks


 *Tharindu Dharmarathna*Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94779109091 <+94%2077%20910%209091>*

>>>
>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048 <071%20635%208048>* *
>
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

[Isuru Haththotuwa]

On Fri, Jan 6, 2017 at 5:19 PM, Uvindra Dias Jayasinha 
wrote:

> Setting a default value for empty fields being sent seems to be best.
>
> Furthermore we can have default values set in our DTO objects in case a
> given field is omitted altogether.
>
> So handling both the above scenarios can overcome the limitation in Oracle.
>
> But I dont know if this is good for the REST API user experience, when
> retrieving data that contains these default values.
>
Additionally this could affect the user experience in UIs as well.

How about we just keep a default value to NULL in DB level and then filter
it from UI? Since anyway Oracle treats zero length String as NULLs, even if
the user enters an empty String it will then be automatically. The rest API
will still return the default value if invoked directly though.

>
> On 6 January 2017 at 15:28, Tharindu Dharmarathna 
> wrote:
>
>>
>>
>> On Fri, Jan 6, 2017 at 3:26 PM, Tharindu Dharmarathna > > wrote:
>>
>>> Hi All,
>>>
>>> I faced $Subject in Oracle database while running integration test on C5
>>> on top.
>>>
>>> *Observation*
>>>
>>> when insert empty string ("") it was save as null in database.
>>>
>>> While going through SO I had found [1] , which did happen in oracle
>>> database.
>>>
>>>
>>> We have come up with several ways to handle empty strings which user
>>> sends through the rest api.
>>>
>>> 1.  Validate the request and send error when giving empty strings
>>> 2.  Set default value like "N/A" into the fields which send as empty.
>>>
>>> Is there any other way to handle this problem ?.
>>>
>>> [1] - http://stackoverflow.com/questions/13278773/null-vs-empty-
>>> string-in-oracle
>>>
>>> Thanks
>>>
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

[Gayan Gunawardana]

On Sun, Jan 8, 2017 at 5:06 PM, Ishara Cooray  wrote:

> Hi Tharindu,
>
> How about storing space character instead of empty string. i have not
> tried it in Oracle db but if that works IMO there will not be an effect on
> user experience.
>
Yes according to [1] storing space character is a good option.

[1]
http://tharindue.blogspot.com/2015/05/cross-database-programming-tips-for.html

>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512 <+94%2077%20262%209512>
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Fri, Jan 6, 2017 at 5:19 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Setting a default value for empty fields being sent seems to be best.
>>
>> Furthermore we can have default values set in our DTO objects in case a
>> given field is omitted altogether.
>>
>> So handling both the above scenarios can overcome the limitation in
>> Oracle.
>>
>> But I dont know if this is good for the REST API user experience, when
>> retrieving data that contains these default values.
>>
>> On 6 January 2017 at 15:28, Tharindu Dharmarathna 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 6, 2017 at 3:26 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Hi All,

 I faced $Subject in Oracle database while running integration test on
 C5 on top.

 *Observation*

 when insert empty string ("") it was save as null in database.

 While going through SO I had found [1] , which did happen in oracle
 database.


 We have come up with several ways to handle empty strings which user
 sends through the rest api.

 1.  Validate the request and send error when giving empty strings
 2.  Set default value like "N/A" into the fields which send as empty.

 Is there any other way to handle this problem ?.

 [1] - http://stackoverflow.com/questions/13278773/null-vs-empty-
 string-in-oracle

 Thanks


 *Tharindu Dharmarathna*Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94779109091 <+94%2077%20910%209091>*

>>>
>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>> ___
>> 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
>
>


-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Kasun Bandara]

Hi IS team,

Tested the following on the Identity Server 5.3.0-RC3 pack,


   - Email Internationalisation Feature (Tenant wise support)
  - Email Templates type addition
  - Email Templates addition
  - Update and Delete Email templates
   - HTML support for email template management (Tenant wise support))

[+] Stable - go ahead and release

Regards.
Kasun

Kasun Gayan Bandara
PhD Research Student
Machine Learning Group

Faculty of Information Technology, Clayton
Monash University
25 Exhibition Walk, Clayton Campus
Wellington Road
Clayton VIC 3800
Australia.

E: herath.band...@monash.edu
M (+61) 43 491 6476





On Mon, Jan 9, 2017 at 6:05 AM, Farasath Ahamed  wrote:

> Tested the following on the Identity Server 5.3.0-RC3 pack,
>
>- Create Service Provider by importing SAML metadata file.
>- Export Resident IDP metadata.
>- SAML SSO for apps hosted on Apache2 using mod_auth_mellon with
>Identity Server.
>- Verify CSRF protection for dashboard apps.
>- Verify IDENTITY- 
>- Verify IDENTITY-5563 
>- Recover Password with user locale based challenge questions.
>- Add User account association between two local user accounts.
>
>  [+] Stable - go ahead and release
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
> On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
> wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> This release fixes the following issues:
>>
>> Runtime : https://wso2.org/jira/issues/?filter=13612
>> Analytics : https://wso2.org/jira/issues/?filter=13614
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
>> Analytics : https://github.com/wso2/anal
>> ytics-is/releases/tag/v5.3.0-rc3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 Identity Server Team -
>>
>> --
>> *Pulasthi Mahawithana*
>> Senior Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022 <+94%2071%20517%209022>
>> Blog: http://blog.pulasthi.org
>>
>> 
>>
>> ___
>> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.3.0- RC3

[Farasath Ahamed]

Tested the following on the Identity Server 5.3.0-RC3 pack,

   - Create Service Provider by importing SAML metadata file.
   - Export Resident IDP metadata.
   - SAML SSO for apps hosted on Apache2 using mod_auth_mellon with
   Identity Server.
   - Verify CSRF protection for dashboard apps.
   - Verify IDENTITY- 
   - Verify IDENTITY-5563 
   - Recover Password with user locale based challenge questions.
   - Add User account association between two local user accounts.

 [+] Stable - go ahead and release


Thanks,
Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 




On Fri, Jan 6, 2017 at 10:06 PM, Pulasthi Mahawithana 
wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 Identity Server 5.3.0.
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> This release fixes the following issues:
>
> Runtime : https://wso2.org/jira/issues/?filter=13612
> Analytics : https://wso2.org/jira/issues/?filter=13614
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-is/releases/tag/v5.3.0-rc3
> Analytics : https://github.com/wso2/analytics-is/releases/tag/v5.3.0-
> rc3
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 Identity Server Team -
>
> --
> *Pulasthi Mahawithana*
> Senior Software Engineer
> WSO2 Inc., http://wso2.com/
> Mobile: +94-71-5179022 <+94%2071%20517%209022>
> Blog: http://blog.pulasthi.org
>
> 
>
> ___
> 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

[Dev] WSO2 Carbon Unified UI Framework 1.0.0-M9 Released!

[SajithAR Ariyarathna]

Hi All,

We are pleased to announce the *ninth milestone* of WSO2 Carbon Unified UI
Framework (UUF). You can download the UUF server distribution at [1].

UUF is an UI framework that let webapp developers to build shareable UI
components and to build webapps by composing those UI components.


*Changes list*:

   - Changes in configuration files.
  - config.yaml, bindings.yaml files are no longer supported for apps
  and components.
  - For components,
 - Component has only component.yaml configuration file. (see sample
 

 )
 - UI specific REST APIs, zone-fragments bindings, business-logic
 related configurations can be defined.
 - Mandatory, without that component won't be deployed.
  - For apps,
 - app.yaml (see sample
 

 )
- Default theme name, menus, URI of error pages, login page
URI, and security related configurations can be defined.
- Mandatory, without that app won't be deployed.
 - component.yaml (see sample
 

 )
- Same as in a component.
 - For themes,
 - theme.yaml is mandatory. (see sample
 

 )
  - Menus are configured at the app level in the app.yaml configuration
  file. (see sample
  

  )
   - Support for deploying UI specified REST APIs.
  - UUF can deploy configured (in component.yaml
  
)
  microservices (using MSF4J
  ) as REST APIs.
  Deployed REST APIs will be available under
  ///apis/ context.
   - Support to push multiple fragments to a zone.
  - Through bindings (configured in component.yaml
  
),
  multiple fragments (in a specified order) can be pushed into a zone.
   - Support to define back-end bundles of a component in the component's
   pom.xml. (see sample
   

   )
   - Following Handlebars helpers are added,
  - {{template}} helper.
 - Can send a server-side Handlebars template (a fragment or an
 inline template) safely to the client-side.
  - String manipulation helpers.
 - abbreviate, capitalize, capitalizeFirst, center, cut, dateFormat
 , defaultIfEmpty, join, ljust, lower, now, numberFormat, replace,
 rjust, slugify, stringFormat, stripTags, substring, upper, wordWrap
 , yesno (see Features App sample
  for
 usage)
  - Added more samples (see Features App
   )
   - Bug fixes.


*Found an issue?*

Help us to improve. Use our GitHub issues page at [2] to report it to us.


[1]
https://github.com/wso2/carbon-uuf/releases/download/v1.0.0-m9/wso2uuf-1.0.0-m9.zip
[2] https://github.com/wso2/carbon-uuf/issues

*-- WSO2 Platform Team--*
Thanks.
-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

[Rukshan Premathunga]

Hi Tharindu,

If a field allow empty string, which mean it is optional right? So we can
consider it as a null right? But when we try to save empty string on a DB,
if it is persist in a differently, it is better to have a default value
since it will be consistent on all the DBs. So can we set the default value
as NULL here? because even if we persist value as a empty string it is not
a valid value for us.
If so, i think it will help to compare values easily as well.

WDYT?

Thanks and Regards

On Sun, Jan 8, 2017 at 5:06 PM, Ishara Cooray  wrote:

> Hi Tharindu,
>
> How about storing space character instead of empty string. i have not
> tried it in Oracle db but if that works IMO there will not be an effect on
> user experience.
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512 <+94%2077%20262%209512>
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Fri, Jan 6, 2017 at 5:19 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Setting a default value for empty fields being sent seems to be best.
>>
>> Furthermore we can have default values set in our DTO objects in case a
>> given field is omitted altogether.
>>
>> So handling both the above scenarios can overcome the limitation in
>> Oracle.
>>
>> But I dont know if this is good for the REST API user experience, when
>> retrieving data that contains these default values.
>>
>> On 6 January 2017 at 15:28, Tharindu Dharmarathna 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 6, 2017 at 3:26 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Hi All,

 I faced $Subject in Oracle database while running integration test on
 C5 on top.

 *Observation*

 when insert empty string ("") it was save as null in database.

 While going through SO I had found [1] , which did happen in oracle
 database.


 We have come up with several ways to handle empty strings which user
 sends through the rest api.

 1.  Validate the request and send error when giving empty strings
 2.  Set default value like "N/A" into the fields which send as empty.

 Is there any other way to handle this problem ?.

 [1] - http://stackoverflow.com/questions/13278773/null-vs-empty-
 string-in-oracle

 Thanks


 *Tharindu Dharmarathna*Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94779109091 <+94%2077%20910%209091>*

>>>
>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>> ___
>> 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
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

[Ishara Cooray]

Hi Tharindu,

How about storing space character instead of empty string. i have not tried
it in Oracle db but if that works IMO there will not be an effect on user
experience.

Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Fri, Jan 6, 2017 at 5:19 PM, Uvindra Dias Jayasinha 
wrote:

> Setting a default value for empty fields being sent seems to be best.
>
> Furthermore we can have default values set in our DTO objects in case a
> given field is omitted altogether.
>
> So handling both the above scenarios can overcome the limitation in Oracle.
>
> But I dont know if this is good for the REST API user experience, when
> retrieving data that contains these default values.
>
> On 6 January 2017 at 15:28, Tharindu Dharmarathna 
> wrote:
>
>>
>>
>> On Fri, Jan 6, 2017 at 3:26 PM, Tharindu Dharmarathna > > wrote:
>>
>>> Hi All,
>>>
>>> I faced $Subject in Oracle database while running integration test on C5
>>> on top.
>>>
>>> *Observation*
>>>
>>> when insert empty string ("") it was save as null in database.
>>>
>>> While going through SO I had found [1] , which did happen in oracle
>>> database.
>>>
>>>
>>> We have come up with several ways to handle empty strings which user
>>> sends through the rest api.
>>>
>>> 1.  Validate the request and send error when giving empty strings
>>> 2.  Set default value like "N/A" into the fields which send as empty.
>>>
>>> Is there any other way to handle this problem ?.
>>>
>>> [1] - http://stackoverflow.com/questions/13278773/null-vs-empty-
>>> string-in-oracle
>>>
>>> Thanks
>>>
>>>
>>> *Tharindu Dharmarathna*Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>
> ___
> 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