Re: [Dev] [Architecture] [Iam-dev] [VOTE] Release WSO2 Identity Server 5.11.0 RC1
Hi All, Tested the following and no blocking issues found, 1. Workflow user approval with the role and users 2. User self-registration (UniqueIDJDBCUserStoreManager secondary user store) 3. Ask Password 4. SAML SSO/SLO 5. Identity Federation with google. 6. EmailOTP (Primary and secondary user store (UniqueIDJDBCUserStoreManager)) [+] Stable - go ahead and release Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] [Announce] WSO2 Carbon Kernel 4.6.1 Released!
Hi All, The WSO2 Engineering Team is pleased to announce the release of WSO2 Carbon Kernel version 4.6.1 <https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1>. WSO2 Carbon is the award-winning, component-based, service-oriented platform for the enterprise-grade WSO2 middleware products stack. It is a 100% open source and delivered under Apache License 2.0. The WSO2 Carbon platform is lean, high-performant, and consists of a collection of OSGi bundles. *What is new in this Release* - Improvements and Bug Fixes <https://github.com/wso2/carbon-kernel/milestone/31?closed=1> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer list: dev@wso2.org | Subscribe | Mail Archive <https://wso2.markmail.org/search/list:org.wso2.dev> - User forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2carbon> Reporting Issues We encourage you to report issues, improvements, documentation faults, and feature requests regarding WSO2 Carbon Kernel through our public WSO2 Carbon Kernel GIT Issues <https://github.com/wso2/carbon-kernel/issues>. Support We are committed to ensuring your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology. For more details and to take advantage of this unique opportunity http://wso2 .com/support/ - The WSO2 Engineering Team - Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC2
Hi All, Thanks for testing WSO2 Carbon Kernel 4.6.1 RC2. Since this vote passed with 7 [+1]s and 0 [-1], we’re hereby closing this vote and proceeding with the WSO2 Carbon Kernel 4.6.1 GA release. Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Wed, Nov 11, 2020 at 2:52 PM Shanika Wickramasinghe wrote: > Hi All, > > I have tested the following related to kernel. > > - User Management with uniqueid jdbc userstore as primary userstore with > mssql 2019 as the DB type > - Role Management with uniqueid jdbc userstore as primary userstore with > mssql 2019 as the DB type > - SCIM2 user listing operations with uniqueid jdbc userstore as primary > userstore with mssql 2019 as the DB type > > Didn't found issues related to the above 3 use cases. > > [+] Stable - go ahead and release > > Thanks, > Shanika > > > > On Sat, Nov 7, 2020 at 3:06 PM Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> Hi Devs, >> >> *WSO2 Carbon Kernel 4.6.1 RC2 Release Vote*. >> >> Please download and test your products with kernel 4.6.1 RC2 and vote. >> The vote will be open for 72 hours or longer as needed. >> >> *Maven staging repository:* >> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4915 >> >> *The tag to be voted upon:* >> https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC2 >> >> [- ] Broken - do not release (explain why) >> [+] Stable - go ahead and release >> >> Thanks >> Kanapriya Kuleswararajan >> Senior Software Engineer >> Mobile : - 0774894438 >> Mail : - kanapr...@wso2.com >> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >> WSO2, Inc. >> lean . enterprise . middleware >> >> > > -- > *Shanika Wickramasinghe* > Software Engineer - QA Team > > Email: shani...@wso2.com > Mobile : +94713503563 > Web : http://wso2.com > > <http://wso2.com/signature> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC2
Hi Devs, *WSO2 Carbon Kernel 4.6.1 RC2 Release Vote*. Please download and test your products with kernel 4.6.1 RC2 and vote. The vote will be open for 72 hours or longer as needed. *Maven staging repository:* https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4915 *The tag to be voted upon:* https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC2 [- ] Broken - do not release (explain why) [+] Stable - go ahead and release Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC1
Hi All We have identified an issue with RC1. So we are dropping the vote. We will release RC2 as soon as possible. Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Sat, Nov 7, 2020 at 2:21 AM Isura Karunaratne wrote: > Hi Kanapriya, > > -1 for the release due to a security issue found in StartTLS in LDAP. > > The fix is available in [1] > > [1] https://github.com/wso2/carbon-kernel/pull/2835 > > Cheers, > Isura. > > On Fri, Nov 6, 2020 at 9:29 PM Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> Hi Devs, >> >> *WSO2 Carbon Kernel 4.6.1 RC1 Release Vote*. >> >> Please download and test your products with kernel 4.6.1 RC1 and vote. >> The vote will be open for 72 hours or longer as needed. >> >> *Maven staging repository:* >> https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4914 >> >> *The tag to be voted upon:* >> https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC1 >> >> [- ] Broken - do not release (explain why) >> [+] Stable - go ahead and release >> >> Thanks >> Kanapriya Kuleswararajan >> Senior Software Engineer >> Mobile : - 0774894438 >> Mail : - kanapr...@wso2.com >> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >> WSO2, Inc. >> lean . enterprise . middleware >> >> > > -- > > *Isura Dilhara Karunaratne* > Technical Lead | WSO2 <http://wso2.com/> > *lean.enterprise.middleware* > Email: is...@wso2.com > Mob : +94 772 254 810 > Blog : https://medium.com/@isurakarunaratne > > > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [VOTE] Release WSO2 Carbon Kernel 4.6.1 RC1
Hi Devs, *WSO2 Carbon Kernel 4.6.1 RC1 Release Vote*. Please download and test your products with kernel 4.6.1 RC1 and vote. The vote will be open for 72 hours or longer as needed. *Maven staging repository:* https://maven.wso2.org/nexus/content/repositories/orgwso2carbon-4914 *The tag to be voted upon:* https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-RC1 [- ] Broken - do not release (explain why) [+] Stable - go ahead and release Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] WSO2 Carbon Kernel 4.6.1-beta2 Released
WSO2 Carbon Kernel 4.6.1-beta2 Released The WSO2 Engineering Team is pleased to announce the release of Carbon Kernel 4.6.1-beta2. It is now available to download from here <https://github.com/wso2/carbon-kernel/releases/tag/v4.6.1-beta2>. Improvements and Bug fixes - https://github.com/wso2/product-is/issues?q=label%3AComponent%2FKernel+milestone%3A5.11.0-Beta4+is%3Aclosed - https://github.com/wso2/product-is/issues?q=label%3AComponent%2FKernel+milestone%3A5.11.0-Beta4+is%3Aopen How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer list: dev@wso2.org | Subscribe | Mail Archive <https://wso2.markmail.org/search/list:org.wso2.dev> - User forum: StackOverflow <http://stackoverflow.com/questions/tagged/wso2carbon> Reporting Issues We encourage you to report issues, improvements, documentation faults, and feature requests regarding WSO2 Carbon Kernel through our public WSO2 Carbon Kernel GIT Issues <https://github.com/wso2/carbon-kernel/issues>. Support We are committed to ensuring your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology. For more details and to take advantage of this unique opportunity http://wso2.com/support/ - The WSO2 Engineering Team - Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. 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.9.0 RC2
Hi All, I have tested the following scenarios and it works as expected, +1 to go ahead and release. - Basic functionality with EmailOTP (Basic authenticator/Federated Authenticator as first step and EmailOTP as the second step) with secondary user stores. - EmailOTP with Email Templates - X509 with basic functionality - Account locking by failed login attempts - User Self Registration Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Fri, Oct 4, 2019 at 1:21 AM Pamoda Wimalasiri wrote: > Hi all, > > I tested the following scenarios on IS-5.9.0-RC2 with MySQL database. > >- Viewing, terminating sessions from the user portal >- Create a service provider, configure SAML SSO, authenticate with >Basic Authenticator for travelocity app >- Create, retrieve and delete Oauth2 app using dcr endpoint >- Configure a federated Identity provider with facebook configuration >- Federated Authentication with facebook >- JIT provisioning with facebook as federated IdP >- Multi option login with basic authenticator and facebook IdP >- Multi-step login with basic authenticator and facebook IdP >- Role-based adaptive authentication > > No blocking issues found. > > [+] Stable - Go ahead and release > > Thanks, > Pamoda > > On Fri, Oct 4, 2019 at 12:24 AM Ayesha Dissanayaka > wrote: > >> Hi, >> >> As I was able to perform the following tests successfully on >> IS-5.9.0-RC2, +1 to go ahead and release. >> >> User self-registration with email confirmation >> >> Username Recovery >> >> Password Recovery >> >> Email OTP >> >> OIDC - auth code flow >> User challenges - self-care REST API >> Browsing management console >> >> [+] Stable - Go ahead and release >> >> Thanks! >> -Ayesha >> >> >> On Thu, Oct 3, 2019 at 10:51 PM Gayashan Bombuwala >> wrote: >> >>> Hi all, >>> >>> Tested below scenarios on IS 5.9.0-RC2 pack. >>> >>>- SAML2 Bearer Assertion Profile for OAuth 2.0 >>>- Federated authentication with a second instance of IS as the >>>Identity Provider. >>>- JIT provisioning with a second instance of IS as the Identity >>>Provider. >>> >>> No blocking issues found. >>> >>> [+] Stable - Go ahead and release >>> >>> Best regards, >>> Gayashan. >>> >>> On Thu, Oct 3, 2019 at 9:16 PM Vihanga Liyanage >>> wrote: >>> >>>> Hi all, >>>> >>>> Tested below scenarios on IS 5.9.0-RC2 pack using the Postgresql >>>> database. >>>> >>>>- Add service provider, configured SAML SSO, authenticate with *the >>>>dispatch *sample web app. >>>>- Add new SP with Open ID OAuth/OpenID Connect Configuration and >>>>authenticate with *the playground *sample web app. >>>>- Tested all OAuth/OIDC grant types. >>>>- Manipulated email templates with I18nEmailMgtConfigService admin >>>>service. >>>> >>>> No blocking issues found. >>>> >>>> [+] Stable - Go ahead and release >>>> >>>> Best regards, >>>> Vihanga. >>>> >>>> On Thu, Oct 3, 2019 at 3:45 PM Ashen Weerathunga >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I have tested the following scenarios and no blocking issues found. >>>>> >>>>>- SSO with SAML >>>>>- Federated authentication with Google >>>>>- Federated authentication with Facebook >>>>>- SSO with multi-option and multi-step authentication >>>>>- Role-based Adaptive authentication >>>>> >>>>> [+] Stable - go ahead and release >>>>> >>>>> Thanks, >>>>> Ashen >>>>> >>>>> >>>>> On Thu, Oct 3, 2019 at 2:34 PM Shanika Wickramasinghe < >>>>> shani...@wso2.com> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I have tested the following features and no issues found >>>>>> >>>>>> Ubuntu 16.04 | MSSQL | Embedded Ldap Primary User Store | Super Tenant >>>>>> >>>>>> >>>>>>- >>&
[Dev] Maintaining IS-Archetypes
In the repo [1] we have archetypes for IS extensions and seems they are outdated as it still uses the old dependency of carbon-identity. This need to be improved/refactor in order to make this to a stable with the latest product version. BTW, we couldn't see any specific reason to have all archetypes here under the repo [1]. Hence we thought to move all the IS-related archetypes - To a separate repo? But here we have to decide, how we are going to maintain the releases (major or minor) if we have all the archetypes in the same repo? In this way, there can be chances that some archetypes get released unnecessary (ie, without any changes). - Or else we can keep the archetypes inside the feature repo itself? Appreciate your valuable suggestions on the above? Further, In this effort, we (myself and @Inthi) are planning the following as the initial step: - Refactor the existing archetypes and Making that to work with IS 5.8.0 for now. - Find the best approach to maintain the archetypes (in a single repo or inside the feature repo). - Add more archetypes as part of this effort. We could see a couple of archetypes already developed, but that need to be reviewed and we have to add those to the specific repo. @Inthirakumaaran Tharmakulasingham will share the details on this. - Generate guidance for creating an archetype. Please share your thoughts and suggestions about this effort, that will be very helpful to us to continue on this :) [1] https://github.com/wso2-extensions/archetypes <https://www.google.com/url?q=https://github.com/wso2-extensions/archetypes&sa=D&source=hangouts&ust=1564833739149000&usg=AFQjCNFopSwDYqHH3VV8GZORIXe7CmhGTQ> Thanks Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail: - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean. enterprise. middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release WSO2 Identity Server 5.8.0 RC3
Hi All, Resend the vote as I couldn't find my name in the archive. Tested the following and It works fine. - Basic functionality with EmailOTP (Basic authenticator/Federated Authenticator as first step and EmailOTP as the second step) - EmailOTP with Email Templates - TOTP with basic functionality - X509 with basic functionality - Tried EmailOTP/TOTP with secondary user stores. [+1] Stable - go ahead and release Kanapriya Kuleswararajan Senior Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Wed, May 22, 2019 at 7:46 PM Hasanthi Purnima Dissanayake < hasan...@wso2.com> wrote: > Hi All, > > We had an issue receiving the replies to this thread and seems some of the > replies have lost due to this. Hence if you have sent a vote and it is not > available in the archive [1] please re-send the vote. All the votes we > received are positive once, so we are planing to close the vote with in few > hours. If you have any concerns please raise ASAP. > > [1] https://wso2.markmail.org/thread/xuyn7ilrts2xvdsn > > Thanks, > Hasanthi > > On Wed, May 22, 2019 at 5:15 PM Hasanthi Purnima Dissanayake < > hasan...@wso2.com> wrote: > >> Hi All, >> >> I have tested following features. >> >>1. OIDC backchannel logout >>2. SAML front channel logout. >> >> No blocking issues found. >> >> [+] Stable - go ahead and release. >> >> Thanks, >> Hasanthi >> >> >> >> On Wed, May 22, 2019 at 8:03 AM Isuranga Perera >> wrote: >> >>> All: >>> I have tested Federated Authentication >>> [+] Stable - go ahead and release. >>> >>> Best Regards >>> Isuranga Perera >>> >>> On Sun, May 19, 2019 at 7:30 PM Shanika Wickramasinghe < >>> shani...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> I have tested the SAML SSO with POST binding and Redirect binding flows >>>> and no issues found. >>>> >>>> +1 Go Ahead and Release >>>> >>>> >>>> Thanks, >>>> >>>> Shanika >>>> >>>> On Thu, May 16, 2019 at 12:33 PM Hasanthi Purnima Dissanayake < >>>> hasan...@wso2.com> wrote: >>>> >>>>> Hi All, >>>>> >>>>> The reason of breaking the RC2 vote is because it is reported an >>>>> unused commented configuration description in carbon.xml [1]. From RC3 >>>>> release that commented line in the configuration file is removed and no >>>>> other code level changes done. >>>>> >>>>> Further in the Analytics-IS pack, the versions are updated according >>>>> to the latest released SP pack versions [2]. >>>>> >>>>> [1] [Dev][VOTE] Release WSO2 Identity Server 5.8.0 RC2 >>>>> [2] [VOTE] Release of WSO2 Stream Processor 4.4.0 RC6 >>>>> >>>>> Thanks, >>>>> Hasanthi >>>>> >>>>> On Thu, May 16, 2019 at 12:30 PM Hasanthi Purnima Dissanayake < >>>>> hasan...@wso2.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> We are pleased to announce the third release candidate of WSO2 >>>>>> Identity Server 5.8.0. >>>>>> >>>>>> This release fixes the following issues, >>>>>> >>>>>>- 5.8.0-RC3 fixes >>>>>><https://github.com/wso2/product-is/milestone/84?closed=1> >>>>>>- 5.8.0-RC2 fixes >>>>>><https://github.com/wso2/product-is/milestone/82?closed=1> >>>>>>- 5.8.0-RC1 fixes >>>>>><https://github.com/wso2/product-is/milestone/78?closed=1> >>>>>>- 5.8.0-Beta5 fixes >>>>>><https://github.com/wso2/product-is/milestone/80?closed=1> >>>>>>- 5.8.0-Beta4 fixes >>>>>><https://github.com/wso2/product-is/milestone/79?closed=1> >>>>>>- 5.8.0-Beta3 fixes >>>>>><https://github.com/wso2/product-is/milestone/77?closed=1> >>>>>>- 5.8.0-Beta fixes >>>>>><https://github.com/wso2/product-is/milestone/75?closed=1> >>>>>>- 5.8.0-Alpha5 fixes >>>>>><https://github.com/wso2/product-is/milestone/74?closed=1> >>>>&
Re: [Dev] Fwd: Wso2 Identity Server: identity-inbound-auth-cas
Hi Mohammed Yousef, Actually, CAS service URL is the identifier of the application that the client is trying to access. In almost all cases, this will be the URL of the application (https://[server-address]/cas-client-webapp/) and the server-address should always point to the location where this sample application (cas-client-webapp) is deployed. If I understood you correctly, you are setting Service Url: https://test.kfupm.edu.sa in the service provider configuration and trying to access that service using some other URL say https://test.kfupm.edu.sa/en/?next=/details and you end up with 500 internal server error. If that so, the reason for this error is, When we processing the login response we are getting the serviceUrlFromRequest [1] (ie, https://test.kfupm.edu.sa/en/?next=/details) and with this URL, the service provider details get retrieved [2]. Since you are not registering the service provider with the service URL: https://test.kfupm.edu.sa/en/?next=/details it returns the default service provider configurations. That causes an issue here. As a workaround, you may extend the source code [3] and you may pass the exact base URL of the service instead of getting the service URL from the request then hopefully, it will give the exact service provider configurations. [1] https://github.com/wso2-extensions/identity-inbound-auth-cas/blob/master/components/cas-inbound-authenticator/src/main/java/org/wso2/carbon/identity/sso/cas/processor/SSOLoginProcessor.java#L77 [2] https://github.com/wso2-extensions/identity-inbound-auth-cas/blob/master/components/cas-inbound-authenticator/src/main/java/org/wso2/carbon/identity/sso/cas/util/CASSSOUtil.java#L120 [3] https://github.com/wso2-extensions/identity-inbound-auth-cas Thanks, Kanapriya Kuleswararajan Software Engineer Mobile : - 0774894438 Mail: - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean. enterprise. middleware On Wed, Feb 6, 2019 at 3:47 PM Shakila Sasikaran wrote: > [Forwarding to dev] > > -- Forwarded message - > From: Mohammed Yousef M. Alnajdi > Date: Tue, Feb 5, 2019 at 3:31 PM > Subject: Wso2 Identity Server: identity-inbound-auth-cas > To: dev@wso2.org > Cc: shak...@wso2.com > > > > Greeting Team, > > I would like to express that i am really grateful to the work you guys put > for the open source community. > > I have 1 small comment/issue regarding the "identity-inbound-auth-cas" i > will try to describe my issue and how i want to solve it. > > >- I configured a new service provider with the name test.kfupm.edu.sa >- I configured the CAS URL as https://test.kfupm.edu.sa >- If i go now to https://test.kfupm.edu.sa everything works fine and i >can see in the url i am getting the sp=test.kfupm.edu.sa >but when i try to have anything like this >https://test.kfupm.edu.sa/en/?next=/details the cas configuration >won't work and i would get the sp=default. >So the issue is i can only have 1 url for cas i want it accept and >check for the base url which is https://test.kfupm.edu.sa which should >be >enough for CAS to find out which SP it is. > > > > https://stackoverflow.com/questions/54396657/how-to-extend-wso2-identity-inbound-auth-cas-to-accept-a-wildcard-url > > Thanks a lot > > *Best Regards.* > *Mohammed Y. Alnajdi.* > *Software Developer.* > *ICTC - Solution Delivery Team.* > > ___ > 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] WSO2 ISO8583 Connector
Hi, You can find the source code for ISO8583 connector [1] and ISO8583 inbound [2] and Please follow the documentation [3] to configure this with WSO2 ESB/EI. Further you can check the blog post [4] which has detailed explanation about this inbound and connector scenario. [1] https://github.com/wso2-extensions/esb-connector-iso8583 [2] https://github.com/wso2-extensions/esb-inbound-iso8583 [3] https://docs.wso2.com/display/ESBCONNECTORS/ISO8583+Connector+and+Inbound+Endpoint [4] http://kkanapriya.blogspot.com Thanks, Kanapriya Kanapriya Kuleswararajan Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Fri, Jun 29, 2018 at 1:44 PM, Herlambang Priantoro wrote: > Hi Kanapriya > Could you give an example about how to implement ISO8583 connector in WSO2 > ESB / Enterprise Integrator, i already follow the tutorial in internet but > still not successfull > > -- > Regards, > > *Herlambang Priantoro* > > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Token2 Authenticator] Getting the error with IS 5.3.0 , IS 5.4.0 and IS 5.4.1 pack
Hi Kalayarasi,
- support-dev-group@ and + dev@
Try the following to get claim values from user-store.
Map userClaimValues =
userRealm.getUserStoreManager().getUserClaimValues(username, new
String[]{claimURI}, null);
Thanks,
Kanapriya
Kanapriya Kuleswararajan
Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
WSO2, Inc.
lean . enterprise . middleware
On Tue, May 22, 2018 at 1:38 PM, Kalaiyarasi Ganeshalingam <
kalaiyar...@wso2.com> wrote:
> Hi All,
>
> I have configured the token2 authenticator with IS 5.3.0 , IS 5.4.0 , IS
> 5.4.1 and IS 5.5.0. It's worked with IS 5.5.0 and didn't work with other IS
> pack. I got the error [1] from backend.I debugged the code and found the
> point [2] that was produced the error. Why I couldn't get the User Id from
> userClaimValues?
>
> [1] ERROR {org.wso2.carbon.identity.application.authentication.
> framework.handler.step.impl.DefaultStepHandler} - Token2 UserId is null
> org.wso2.carbon.identity.application.authentication.framework.exception.AuthenticationFailedException:
> Token2 UserId is null
>
> [2] userId = userRealm.getUserStoreManager().getUserClaimValue(username,
> Token2Constants.USERID_CLAIM, null);
>
> Regards,
> Kalai
>
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org&sa=D&sntz=1&usg=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
> Tel:+94 076 6792895
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] IDP initiated single logout Vs Federated Initiated single logout
Hi All, As I'm working on [1], I need to get some clarifications regarding $Subject, AFAIU, Federated IDP initiated logout means other third party identity provider such as Salesforce, Google IDP, Shibboleth and etc initiated logout request where as IDP initiated logout request means WSO2 IS initiated logout request. Please correct me If I'm wrong? If FIDP and IDP initiated logout request are two different thing, then can anyone point me out the official WSO2 document link [2], [3] to setup the Federated IDP initiated logout in WSO2 IS. I'm able to find the following references but it is highlighted as IDP initiated logout. [1] Federated IdP Initiated Logout [2] http://daytodayjava.blogspot.com/2015/08/saml2-idp-initiated-single-logout-with.html [3] https://docs.wso2.com/display/IS530/Configuring+Single+Sign-On#ConfiguringSingleSign-On-ConfiguringtheSSOwebapplication Thanks, Kanapriya Kuleswararajan Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Commenting out addressing module of axis2.xml for email OTP
Hi Omindu, AFAIK, When we did the EmailOTP connector, we got an error "The system is attempting to engage a module that is not available: addressing" while creating the configuration context from axis2 file . So that we have commented out the following module from axis2.xml file. **Please refer [1] for more clarifications. [1] [Dev] Unable to create configuration context from axis2.xml - with wso2is-5.2.0-alpha Thanks, Kanapriya Kanapriya Kuleswararajan Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ WSO2, Inc. lean . enterprise . middleware On Mon, Jan 15, 2018 at 10:43 AM, Omindu Rathnaweera wrote: > Hi Team, > > Is anyone aware of the reason why we have to do the following > configuration for Email OTP [1] in axis2.xml (See instruction No.3 in > 'Enabling email configuration on WSO2 IS' section) ? > > '*Comment out the property to avoid syntax > errors*.' > > IMO saying '*to avoid syntax errors*' doesn't make much sense. > > [1] - https://docs.wso2.com/display/IS540/Configuring+Email+OTP > > Thanks, > Omindu. > > -- > Omindu Rathnaweera > Senior Software Engineer, WSO2 Inc. > Mobile: +94 771 197 211 <+94%2077%20119%207211> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I reset secret key of a federated identity when using TOTP
> > +1. In that case, can you explain this expectation in the JIRA. Because, > JIRA just includes the error and does not mention how the flow should be. > Updated the JIRA with the relevant information. > > >> >> That's the reason for raising this JIRA. >> >> 3. For the case I tried, where in first step user authenticates with >>> Google and in the second step TOTP comes, the user didn't get associated >>> with the local user even though I have configured so. Still TOTP worked but >>> the problem was there was no way to enforce re-scanning of the QR code. >>> Given the fact, I too think user should always be associated for a local >>> user, or if such a user is not found may be JIT provision the federated >>> user (may be by honouring the JIT provisioning config). Else the end to end >>> authentication flow should fail with appropriate error messages. >>> >>> >>> >>>> >>>>> [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ >>>>> Authenticator >>>>> >>>>> Thanks >>>>> >>>>> >>>>> Kanapriya Kuleswararajan >>>>> Software Engineer | WSO2 >>>>> Mobile : - 0774894438 >>>>> Mail : - kanapr...@wso2.com >>>>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >>>>> >>>>> On Mon, Oct 23, 2017 at 11:51 PM, Malithi Edirisinghe < >>>>> malit...@wso2.com> wrote: >>>>> >>>>>> Hi Team, >>>>>> >>>>>> I configured two step authentication with google federated >>>>>> authentication and TOTP for a service provider; i.e, first step is >>>>>> configured to use google as federated IdP, second step is TOTP. >>>>>> Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' >>>>>> is set to true in TOTP authenticator configuration in >>>>>> application-authentication.xml file, such that TOTP is enforced and can >>>>>> enrol user while login. >>>>>> >>>>>> Now, when trying to access the SP, Google login page popped up for >>>>>> which user credentials were provided and authenticated. Then, in the next >>>>>> step, TOTP propose to enrol the user by scanning the QR code which was >>>>>> done. The federated user logged in successfully. >>>>>> >>>>>> Now, suppose I want to refresh the secret key of this account or >>>>>> clear it, such that the user needs to scan the QR code again. This could >>>>>> be >>>>>> done for a local user as the secret key was stored under ' >>>>>> http://wso2.org/claims/identity/secretkey' claim. But, for the user >>>>>> federated over google this could not be done. And I'm not sure where do >>>>>> we >>>>>> store the secret key for this account. >>>>>> >>>>>> Appreciate your input. >>>>>> >>>>>> Thanks, >>>>>> Malithi. >>>>>> >>>>>> -- >>>>>> >>>>>> *Malithi Edirisinghe* >>>>>> Associate Technical Lead >>>>>> WSO2 Inc. >>>>>> >>>>>> Mobile : +94 (0) 718176807 >>>>>> malit...@wso2.com >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Malithi Edirisinghe* >>>>> Associate Technical Lead >>>>> WSO2 Inc. >>>>> >>>>> Mobile : +94 (0) 718176807 >>>>> malit...@wso2.com >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> *Malithi Edirisinghe* >>> Associate Technical Lead >>> WSO2 Inc. >>> >>> Mobile : +94 (0) 718176807 >>> malit...@wso2.com >>> >> >> > > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I reset secret key of a federated identity when using TOTP
Hi Malithi, > > I'm still confused on the expectation here. > 1. When TOTP is enabled as second factor for a federated login scenario, > should that federated identity be always mapped with a local account ? > Yes, that is how these use-cases are working in federated scenario. > 2. If (1) should hold, that means during the authentication flow, if the > association fails the end to end authentication should fail as well. From, > the JIRA that you have created, I don't think this is what's being > highlighted. > Earlier , we had failed the authentication flow when if there is no user found in active directory, then there was a concern to handle this flow by endup with first step rather make the flow fails. But based on the internal discussion, we handle this with specific condition in SMSOTP and EmailOTP. Say, In SMSOTP we handled this flow by having a parameter and if that parameter set as true then allow the user to enter a mobile number in authentication flow and if not redirect the user to error page with specific error message. In my concern, Since these use-cases are same for all these three authenticators , Don't we need to handle this flow in TOTP as well by end up with first step or redirecting the user to error page? That's the reason for raising this JIRA. 3. For the case I tried, where in first step user authenticates with Google > and in the second step TOTP comes, the user didn't get associated with the > local user even though I have configured so. Still TOTP worked but the > problem was there was no way to enforce re-scanning of the QR code. > Given the fact, I too think user should always be associated for a local > user, or if such a user is not found may be JIT provision the federated > user (may be by honouring the JIT provisioning config). Else the end to end > authentication flow should fail with appropriate error messages. > > > >> >>> [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ >>> Authenticator >>> >>> Thanks >>> >>> >>> Kanapriya Kuleswararajan >>> Software Engineer | WSO2 >>> Mobile : - 0774894438 >>> Mail : - kanapr...@wso2.com >>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >>> >>> On Mon, Oct 23, 2017 at 11:51 PM, Malithi Edirisinghe >> > wrote: >>> >>>> Hi Team, >>>> >>>> I configured two step authentication with google federated >>>> authentication and TOTP for a service provider; i.e, first step is >>>> configured to use google as federated IdP, second step is TOTP. >>>> Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is >>>> set to true in TOTP authenticator configuration in >>>> application-authentication.xml file, such that TOTP is enforced and can >>>> enrol user while login. >>>> >>>> Now, when trying to access the SP, Google login page popped up for >>>> which user credentials were provided and authenticated. Then, in the next >>>> step, TOTP propose to enrol the user by scanning the QR code which was >>>> done. The federated user logged in successfully. >>>> >>>> Now, suppose I want to refresh the secret key of this account or clear >>>> it, such that the user needs to scan the QR code again. This could be done >>>> for a local user as the secret key was stored under ' >>>> http://wso2.org/claims/identity/secretkey' claim. But, for the user >>>> federated over google this could not be done. And I'm not sure where do we >>>> store the secret key for this account. >>>> >>>> Appreciate your input. >>>> >>>> Thanks, >>>> Malithi. >>>> >>>> -- >>>> >>>> *Malithi Edirisinghe* >>>> Associate Technical Lead >>>> WSO2 Inc. >>>> >>>> Mobile : +94 (0) 718176807 >>>> malit...@wso2.com >>>> >>> >>> >>> >>> >>> -- >>> >>> *Malithi Edirisinghe* >>> Associate Technical Lead >>> WSO2 Inc. >>> >>> Mobile : +94 (0) 718176807 >>> malit...@wso2.com >>> >> >> > > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Account association with 'userAttribute' usecase in SMSOTP and TOTP
Hi Malithi, Yes, I got your concern, Please find the answers in-line > My question is not about the config issue or it's clarity. My question is > about the way this usecase is being achieved now and is it the way to do it. > That's why I was repeating, "why not use claim transformation to resolve > the local claim (wso2 claim) here". > When we improved these use-cases, we came up with this solutions as per the internal discussion with the product team regarding these use-cases. +1 improving this use-case with claim transformation. Also, as per the present implementation I feel the 'userAttribute' > parameter configuration in the TOTP or SMSOTP authenticator config is > redundant, as the respective claim is being configured per each federated > authenticator. > > Thanks, > Malithi. > > On Wed, Oct 25, 2017 at 11:08 AM, Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> Hi Malithi, >> >> 2. Noted, that in each authenticator an additional parameter needs to be >>>> configured to denote 'userAttribute' mapping. Is this how (1) above is >>>> achieved ? >>>> However, the respective configurations in SMSOTP and TOTP with this >>>> regard are not consistent. Moreover, I feel transforming back to the local >>>> dialect and using that to retrieve the attribute to be mapped is the way to >>>> do. With that this becomes a redundant config. >>>> >>> >> For the userAttribute usecase, you can use the parameter name for TOTP, >>> SMSOTP as I mentioned in the above config with the prefix of the >>> authenticator name which is configured as second step. This leads the >>> configurations more consistent. All these things documented in [1]. >>> >> >> >> [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ >>> Authenticator#ConfiguringTOTPAuthenticator-Configuringtheser >>> viceproviderConfiguringtheserviceprovider >>> >> >>> Yes. This is what I highlighted in point (2). To achieve case 1 another >>> parameter needs to be configured per each authenticator. >>> But, what I'm suggesting is to use claim transformation to resolve the >>> local claim. In that case, there is no need to configure a separate >>> parameter per each authenticator. Wondering if this approach is not chosen >>> due to any other complications on resolving back to local claim. >>> >>> Moreover, as I feel the parameter configuration per each authenticator >>> is not well explained in documentation. Also, when it comes to TOTP there >>> is another authenticator config parameter being mentioned in the doc as >>> 'federatedEmailAttributeKey'. What is this for ? It's not explained at all. >>> >>> I also checked this parameter usage in TOTP code base. Couldn't find any >> usage of this. Based on th offline discussion with the team, it seems a >> documentation bug. So that ,I have removed this parameter from the config. >> Thanks for pointing out this. >> >>> >>>> >>>>> 3. For the mapping to happen the claim value resolved should always be >>>>> the local username. Why not mapping can happen over another unique claim >>>>> like email ? >>>>> As I see, we can easily configure this for an ldap, by configuring >>>>> the 'UserNameSearchFilter' to search users over several attributes. >>>>> >>>>> Thanks, >>>>> Malithi >>>>> -- >>>>> >>>>> *Malithi Edirisinghe* >>>>> Associate Technical Lead >>>>> WSO2 Inc. >>>>> >>>>> Mobile : +94 (0) 718176807 >>>>> malit...@wso2.com >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> *Malithi Edirisinghe* >>> Associate Technical Lead >>> WSO2 Inc. >>> >>> Mobile : +94 (0) 718176807 >>> malit...@wso2.com >>> >> >> > > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Account association with 'userAttribute' usecase in SMSOTP and TOTP
Hi Malithi, 2. Noted, that in each authenticator an additional parameter needs to be >> configured to denote 'userAttribute' mapping. Is this how (1) above is >> achieved ? >> However, the respective configurations in SMSOTP and TOTP with this >> regard are not consistent. Moreover, I feel transforming back to the local >> dialect and using that to retrieve the attribute to be mapped is the way to >> do. With that this becomes a redundant config. >> > For the userAttribute usecase, you can use the parameter name for TOTP, > SMSOTP as I mentioned in the above config with the prefix of the > authenticator name which is configured as second step. This leads the > configurations more consistent. All these things documented in [1]. > [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ > Authenticator#ConfiguringTOTPAuthenticator-Configuringtheser > viceproviderConfiguringtheserviceprovider > > Yes. This is what I highlighted in point (2). To achieve case 1 another > parameter needs to be configured per each authenticator. > But, what I'm suggesting is to use claim transformation to resolve the > local claim. In that case, there is no need to configure a separate > parameter per each authenticator. Wondering if this approach is not chosen > due to any other complications on resolving back to local claim. > > Moreover, as I feel the parameter configuration per each authenticator is > not well explained in documentation. Also, when it comes to TOTP there is > another authenticator config parameter being mentioned in the doc as > 'federatedEmailAttributeKey'. What is this for ? It's not explained at all. > > I also checked this parameter usage in TOTP code base. Couldn't find any usage of this. Based on th offline discussion with the team, it seems a documentation bug. So that ,I have removed this parameter from the config. Thanks for pointing out this. > >> >>> 3. For the mapping to happen the claim value resolved should always be >>> the local username. Why not mapping can happen over another unique claim >>> like email ? >>> As I see, we can easily configure this for an ldap, by configuring the >>> 'UserNameSearchFilter' to search users over several attributes. >>> >>> Thanks, >>> Malithi >>> -- >>> >>> *Malithi Edirisinghe* >>> Associate Technical Lead >>> WSO2 Inc. >>> >>> Mobile : +94 (0) 718176807 >>> malit...@wso2.com >>> >> >> > > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I reset secret key of a federated identity when using TOTP
Hi Malithi, > BTW, for both local user and federated user this will work once you > de-select the Enable TOTP claim from the dashboard. Because for the > federated scenario, based on the use-cases have to create the user in the > local user store. If you are not setting any use case, then default (local) > use-case will get involved in the federation scenario. Please refer the > documentation [1] for more info. > So you mean, the federated user always needs to be some how associated with a local user ? If so, if such a local user is not found should it proceed further ? I was using 'userAttribute' usecase to associate with the local account. It worked for SMS OTP but not for TOTP. Will have a check on this again, because as per the code same utilities seems to be used in both cases. Yes, the federated user some how associated with local user to handle with these use-cases and I checked the case such as ,if such user is not found in user store then process gets fails. This should be fixed and I raised a JIRA [1] to track this issue. [1] https://wso2.org/jira/browse/ISCONNECT-91 > > [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ > Authenticator > > Thanks > > > Kanapriya Kuleswararajan > Software Engineer | WSO2 > Mobile : - 0774894438 > Mail : - kanapr...@wso2.com > LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ > > On Mon, Oct 23, 2017 at 11:51 PM, Malithi Edirisinghe > wrote: > >> Hi Team, >> >> I configured two step authentication with google federated authentication >> and TOTP for a service provider; i.e, first step is configured to use >> google as federated IdP, second step is TOTP. >> Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is >> set to true in TOTP authenticator configuration in >> application-authentication.xml file, such that TOTP is enforced and can >> enrol user while login. >> >> Now, when trying to access the SP, Google login page popped up for which >> user credentials were provided and authenticated. Then, in the next step, >> TOTP propose to enrol the user by scanning the QR code which was done. The >> federated user logged in successfully. >> >> Now, suppose I want to refresh the secret key of this account or clear >> it, such that the user needs to scan the QR code again. This could be done >> for a local user as the secret key was stored under ' >> http://wso2.org/claims/identity/secretkey' claim. But, for the user >> federated over google this could not be done. And I'm not sure where do we >> store the secret key for this account. >> >> Appreciate your input. >> >> Thanks, >> Malithi. >> >> -- >> >> *Malithi Edirisinghe* >> Associate Technical Lead >> WSO2 Inc. >> >> Mobile : +94 (0) 718176807 >> malit...@wso2.com >> > > > > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Account association with 'userAttribute' usecase in SMSOTP and TOTP
Hi Malithi, Please find the comments in line. > > I was using $subject to associate federated identity over google and > facebook to the local user while configuring SMSOTP and TOTP as the second > factor authentication mechanism. > > As I noted, for this to work I had to configure the federated claim, as > the userAttribute in the authenticator configuration, from which the > respective local user will be mapped. > Ex: > Added below in Google and Facebook case > email > > 1. The first question is what will happen when multi-option authentication > is configured as the first step? > I tried with Google and Facebook configured as muti-option in the first > step while having 'email' configured as the 'userAttribute'. That worked > because in both, there is a federated claim as 'email'. But, what if some > other authenticator is configured which will not have 'email' claim and > mail address of the user is received over a different claim format ? > As I see, the local claim (wso2 claim) should be configured in the > authenticator configuration and during the authentication flow, local claim > configured in the authenticator config should be picked, and the claim > value should be resolved after transforming federated claims received to > local dialect (wso2 dialect). > > When multi-option configured as first step (Google and Facebook) , and say, if the cliams (email) is different format in both authenticator , then you can have separate config with authenticator name in authentication.xml file as follow. ** *mailaddress* *mailaddress* ** You can have similar config as above for Google authenticator as well. 2. Noted, that in each authenticator an additional parameter needs to be > configured to denote 'userAttribute' mapping. Is this how (1) above is > achieved ? > However, the respective configurations in SMSOTP and TOTP with this regard > are not consistent. Moreover, I feel transforming back to the local dialect > and using that to retrieve the attribute to be mapped is the way to do. > With that this becomes a redundant config. > For the userAttribute usecase, you can use the parameter name for TOTP, SMSOTP as I mentioned in the above config with the prefix of the authenticator name which is configured as second step. This leads the configurations more consistent. All these things documented in [1]. [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+ Authenticator#ConfiguringTOTPAuthenticator-ConfiguringtheserviceproviderC onfiguringtheserviceprovider > > 3. For the mapping to happen the claim value resolved should always be the > local username. Why not mapping can happen over another unique claim like > email ? > As I see, we can easily configure this for an ldap, by configuring the > 'UserNameSearchFilter' to search users over several attributes. > > Thanks, > Malithi > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How can I reset secret key of a federated identity when using TOTP
Hi Malithi, If you wanted to re-scan the QR code then you have to deselect the Enable TOTP claim in the dashboard, this will automatically remove the secret key claim from the user profile. BTW, for both local user and federated user this will work once you de-select the Enable TOTP claim from the dashboard. Because for the federated scenario, based on the use-cases have to create the user in the local user store. If you are not setting any use case, then default (local) use-case will get involved in the federation scenario. Please refer the documentation [1] for more info. [1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+Authenticator Thanks Kanapriya Kuleswararajan Software Engineer | WSO2 Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> On Mon, Oct 23, 2017 at 11:51 PM, Malithi Edirisinghe wrote: > Hi Team, > > I configured two step authentication with google federated authentication > and TOTP for a service provider; i.e, first step is configured to use > google as federated IdP, second step is TOTP. > Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is set > to true in TOTP authenticator configuration in > application-authentication.xml file, such that TOTP is enforced and can > enrol user while login. > > Now, when trying to access the SP, Google login page popped up for which > user credentials were provided and authenticated. Then, in the next step, > TOTP propose to enrol the user by scanning the QR code which was done. The > federated user logged in successfully. > > Now, suppose I want to refresh the secret key of this account or clear it, > such that the user needs to scan the QR code again. This could be done for > a local user as the secret key was stored under 'http://wso2.org/claims/ > identity/secretkey' claim. But, for the user federated over google this > could not be done. And I'm not sure where do we store the secret key for > this account. > > Appreciate your input. > > Thanks, > Malithi. > > -- > > *Malithi Edirisinghe* > Associate Technical Lead > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Couldn't authenticate the Tiqr by scanning QR code with enrolled user
Hi All, I just went through some resources of Tiqr and found out that they make the current version of tiqr supports the OCRA suite of authentication protocols. It's security is based on AES 256-bit encryption and the SHA-family of hash functions. Seems like, based on these changes of authentication mechanism, We couldn't authenticate the user, even-though able to scan the QR code as in the above screen shot which I shared in the initial thread. AFAIU, we have to make/re-write the tiqr-client to support this authenticaton mechanism to make this current app to work. So , for the timing we are deprecated the tiqr authenticator from the store and moved the documentation to the private space. [1] https://apkpure.biz/org.tiqr.authenticator/tiqr [2] https://www.rcdevs.com/solutions/tokens/tiqr/ [3] https://www.rcdevs.com/docs/howtos/tiqr_quick_start/tiqr_quick_start/#1-introduction Thanks Kanapriya Kuleswararajan Software Engineer | WSO2 Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> On Tue, Oct 10, 2017 at 10:13 AM, Kanapriya Kuleswararajan < kanapr...@wso2.com> wrote: > Hi Malaka > >> >> TIQR has changed the mobile app recently and seems they have deprecated >> the support for previous versions. >> >> Can we deprecate the current authinticator? Can we also checking with >> TIQR team the possibility to upgrade? >> >> +1 for deprecate the current authenticator and will do the needfull. > BTW we have used simplesamlphp [1] to deals with tiqr authentication. > Seems we have re-write or modify this client as well to support with latest > tiqr mobile application. > > [1] https://github.com/simplesamlphp/simplesamlphp/tree/v1.14.16 > >> [1] http://privacyidea.readthedocs.io/en/latest/configuration/to >> kens/tiqr.html#tiqr >> >> On Mon, Oct 9, 2017 at 7:00 PM, Malaka Silva wrote: >> >>> Hi Kanapriya, >>> >>> We need to investigate if TIQR has done and api change with the new app. >>> If so we need to deprecate the current authenticator. >>> >>> On Mon, Oct 9, 2017 at 3:27 PM, Shakila Sasikaran >>> wrote: >>> >>>> Hi Kanapriya, >>>> >>>> You can refer the repo [1]. >>>> >>>> [1] https://github.com/simplesamlphp/simplesamlphp >>>> >>>> Thanks >>>> >>>> On Mon, Oct 9, 2017 at 3:04 PM, Shakila Sasikaran >>>> wrote: >>>> >>>>> Hi Kanapriya, >>>>> >>>>> It seems they released new version of tiqr mobile application and this >>>>> issue comes on this latest one. We may need to modify the tiqr client to >>>>> support the latest version. >>>>> >>>>> Thanks >>>>> >>>>> On Mon, Oct 9, 2017 at 2:22 PM, Kanapriya Kuleswararajan < >>>>> kanapr...@wso2.com> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I have tried with Tiqr authenticator [1] as mentioned [2] , I >>>>>> couldn't authenticate the enrolled user by scanning the QR code. I got >>>>>> response as below in the mobile app once I scanned the QR code. >>>>>> >>>>>> Please note that I connected my phone to the same WiFi network on >>>>>> which my tiqr-client is running. >>>>>> >>>>>> [image: Inline image 1] >>>>>> >>>>>> @Shakila : Do you have any idea on this, What could be the reason for >>>>>> this? >>>>>> >>>>>> >>>>>> [1] https://store.wso2.com/store/assets/isconnector/details/9470 >>>>>> 9865-ea3f-478b-bb4d-6f12da1e8274 >>>>>> [2] https://docs.wso2.com/display/ISCONNECTORS/Configuring+Tiqr+ >>>>>> Authenticator >>>>>> >>>>>> >>>>>> Thanks >>>>>> Kanapriya Kuleswararajan >>>>>> Software Engineer | WSO2 >>>>>> Mobile : - 0774894438 <077%20489%204438> >>>>>> Mail : - kanapr...@wso2.com >>>>>> LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ >>>>>> <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Shakila Sasikaran >>>>> Software Engineer >>>>>
[Dev] Couldn't authenticate the Tiqr by scanning QR code with enrolled user
Hi All, I have tried with Tiqr authenticator [1] as mentioned [2] , I couldn't authenticate the enrolled user by scanning the QR code. I got response as below in the mobile app once I scanned the QR code. Please note that I connected my phone to the same WiFi network on which my tiqr-client is running. [image: Inline image 1] @Shakila : Do you have any idea on this, What could be the reason for this? [1] https://store.wso2.com/store/assets/isconnector/details/94709865-ea3f-478b-bb4d-6f12da1e8274 [2] https://docs.wso2.com/display/ISCONNECTORS/Configuring+Tiqr+Authenticator Thanks Kanapriya Kuleswararajan Software Engineer | WSO2 Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Getting error in Integration Cloud
Hi All, I have tried a sample scenario which is discussed in [1] in integration cloud. The scenario works fine in local environment , but sometimes I observed following error in integration cloud. Please find the log below: [2017-08-17 11:16:03,665] INFO - LogMediator Custom Log = Queried from salesforce [2017-08-17 11:16:20,203] WARN - TargetHandler Exception occurred while reading the response Remote Address : wso2438.crm5.dynamics.com/66. 119.154.20:443 [2017-08-17 11:16:20,204] WARN - MultitenantMessageReceiver Tenant domain is not available in tenant request message context, hence it might not be set in the thread local carbon context [2017-08-17 11:16:20,233] ERROR - NativeWorkerPool Uncaught exception org.apache.axis2.engine.AxisError: ServiceContext in OperationContext does not match ! at org.apache.axis2.context.MessageContext.setOperationContext( MessageContext.java:1404) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver. processResponse(MultitenantMessageReceiver.java:144) at org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver.receive( MultitenantMessageReceiver.java:82) at org.apache.synapse.transport.passthru.TargetErrorHandler$1. run(TargetErrorHandler.java:139) at org.apache.axis2.transport.base.threads.NativeWorkerPool$ 1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) If I get this error , then couldn't continue the flow of scenario. What Could be the reason for this? [1] [Architecture] ESB connector smaple scenario - Integrate Salesforce REST with Microsoft dynamics CRM (Account/Contact) Thanks Kanapriya Kuleswararajan Software Engineer | WSO2 Mobile : - 0774894438 Mail : - kanapr...@wso2.com LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/ <https://www.linkedin.com/in/hariprasath-thanarajah-5234b660> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issues while enable the blocking mode
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.config.xml.AnonymousListMediator.mediate(AnonymousListMediator.java:37)
at
org.apache.synapse.config.xml.SwitchCase.mediate(SwitchCase.java:69)
at
org.apache.synapse.mediators.filters.SwitchMediator.mediate(SwitchMediator.java:134)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
at
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:210)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:371)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2017-06-14 15:00:13,988] INFO - LogMediator To:
https://wso21234.crm5.dynamics.com/api/data/v8.2/accounts(31618218-8a4e-e711-80f7-c4346bad279c)?$select=name,creditonhold,address1_latitude,
MessageID: urn:uuid:73a06200-8cf2-4b5d-a03e-d19ee4ff5bdd, Direction:
request, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 401001,
ERROR_MESSAGE = Transport error: 405 Error: Method Not Allowed, Payload:
{"name":"Updated Sample Account"}
[2017-06-14 15:00:13,996] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"HTTP/1.1 202 Accepted[\r][\n]"
[2017-06-14 15:00:13,997] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Date: Wed, 14 Jun 2017 09:30:13 GMT[\r][\n]"
[2017-06-14 15:00:13,997] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Transfer-Encoding: chunked[\r][\n]"
[2017-06-14 15:00:13,997] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"Connection: keep-alive[\r][\n]"
[2017-06-14 15:00:13,997] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"[\r][\n]"
[2017-06-14 15:00:13,997] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"0[\r][\n]"
[2017-06-14 15:00:13,998] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
"[\r][\n]"
Is there any way to resolve this issues? or Is it an expected behavior?
[1] [Architecture] [PET] Microsoft Dynamics CRM Connector
Thanks,
Kanapriya Kuleswararajan
Software Engineer | WSO2
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
<https://www.linkedin.com/in/hariprasath-thanarajah-5234b660>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Getting Anonymous endpoint error via ESB
Hi All ,
I have checked the JIRA [1] and tried with freshdesk connector to resolve
the issue.
The FreshDesk API Endpoint can be invoked directly. But I'm getting
anonymous endpoint error when I tried the endpoint via the ESB.
It seems IP address and the port are appended with the host. What could be
the reason ?
Please find the simplified proxy configuration [2] and the error [3] of
the request.
[1] https://wso2.org/jira/projects/ESBCONNECT/issues/ESBCONNECT-166
[2]
http://ws.apache.org/ns/synapse
<http://www.google.com/url?q=http%3A%2F%2Fws.apache.org%2Fns%2Fsynapse&sa=D&sntz=1&usg=AFQjCNHXEm-DVy-kXjma9HiDSOzvmv4DoA>
"
name="sample"
startOnLoad="true"
statistics="enable"
trace="enable"
transports="http">
http://org.apache.synapse/xsd
<http://www.google.com/url?q=http%3A%2F%2Forg.apache.synapse%2Fxsd&sa=D&sntz=1&usg=AFQjCNHFBE5d7rSVgszJpW_f9GbBWTHLMA>
"
expression="fn:concat('Basic ',
'MFNsWkhRbnI1NkN0cmdsTENNZGU6WA==')"
name="Authorization"
scope="transport"/>
https://kana.freshdesk.com/api/v2/companies/3102315
<https://www.google.com/url?q=https%3A%2F%2Fkana.freshdesk.com%2Fapi%2Fv2%2Fcompanies%2F3102315&sa=D&sntz=1&usg=AFQjCNE6O0m8WtZeuosTCx9-N0Dp5Mg_pw>
"/>
[3]
[2017-06-08 16:39:21,804] INFO - ProxyService Successfully created the
Axis2 service for Proxy service : sample
[2017-06-08 16:39:26,874] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"GET /services/sample HTTP/1.1[\r][\n]"
[2017-06-08 16:39:26,874] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Host: kanapriya-thinkpad-t540p:8280[\r][\n]"
[2017-06-08 16:39:26,874] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Connection: keep-alive[\r][\n]"
[2017-06-08 16:39:26,874] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Cache-Control: no-cache[\r][\n]"
[2017-06-08 16:39:26,874] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/51.0.2704.63 Safari/537.36[\r][\n]"
[2017-06-08 16:39:26,875] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Postman-Token: 12391c14-b6f4-8ac2-7c88-6e00f9e80d0a[\r][\n]"
[2017-06-08 16:39:26,875] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Accept: */*[\r][\n]"
[2017-06-08 16:39:26,875] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Accept-Encoding: gzip, deflate, sdch[\r][\n]"
[2017-06-08 16:39:26,875] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"Accept-Language: en-US,en;q=0.8[\r][\n]"
[2017-06-08 16:39:26,875] DEBUG - wire HTTP-Listener I/O dispatcher-2 >>
"[\r][\n]"
[2017-06-08 16:39:27,384] WARN - TargetHandler Connection closed before
sending request out Remote Address : kana.freshdesk.com/52.72.32.65:443
[2017-06-08 16:39:27,386] INFO - EndpointContext Endpoint : AnonymousEndpoint
with address https://kana.freshdesk.com/api/v2/companies/3102315 has
been marked for SUSPENSION, but no further retries remain. Thus it will be
SUSPENDED.
[2017-06-08 16:39:27,386] WARN - EndpointContext Suspending endpoint :
AnonymousEndpoint with address
https://kana.freshdesk.com/api/v2/companies/3102315 - current suspend
duration is : 3ms - Next retry after : Thu Jun 08 16:39:57 IST 2017
[2017-06-08 16:39:27,387] INFO - LogMediator To:
https://kana.freshdesk.com/api/v2/companies/3102315, MessageID:
urn:uuid:06a1bcf5-e4a7-4212-a039-e9d552a6d3fc, Direction: request, MESSAGE
= Executing default 'fault' sequence, ERROR_CODE = 101505, ERROR_MESSAGE =
Error in Sender, Envelope: http://schemas.xmlsoap.org/soap/envelope/
">
[2017-06-08 16:42:27,055] WARN - SourceHandler Connection time out after
request is read: http-incoming-2 Socket Timeout : 18 Remote Address : /
127.0.0.1:19323
Thanks
Kanapriya Kuleswararajan
Software Engineer | WSO2
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/
<https://www.linkedin.com/in/hariprasath-thanarajah-5234b660>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CAS is not working when the application is a SaaS app
Hi Malaka, I have tested existing cas-inbound-authenticator by enable the SaaS application in super tenant domain and try to login from different tenant domain. But I couldn't login with different tenant domain. I checked with above fix also, It works fine when the application is a SaaS app. Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Tue, Nov 15, 2016 at 5:41 PM, Hasintha Indrajee wrote: > Hi all, > > Please find the below fix for this issue. This includes an API change. > Please review and merge this fix. > > [1] https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/10 > > On Tue, Nov 15, 2016 at 2:52 PM, Malaka Silva wrote: > >> Kanapriya can you have a quick look and update with findings please? >> >> On Tue, Nov 15, 2016 at 11:33 AM, Hasintha Indrajee >> wrote: >> >>> Hi All, >>> >>> CAS is not working when we register a SaaS application and when I am >>> trying to login from a different tenant user. This should be supported by >>> CAS authentication as it is a basic requirement. >>> >>> -- >>> Hasintha Indrajee >>> WSO2, Inc. >>> Mobile:+94 771892453 >>> >>> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Technical Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> https://wso2.com/signature >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> > > > > -- > Hasintha Indrajee > WSO2, Inc. > Mobile:+94 771892453 > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] CAS connector doesnt work with federated authenticators.
Hi, Yes, I have set the relying party in authentication request and now works fine with federated authentication. Please find the updated version [1] in the store. [1] https://store.wso2.com/store/assets/isconnector/list?q=%22_ default%22%3A%22cas%20inbound%22 Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Wed, Nov 2, 2016 at 12:52 PM, Harsha Thirimanna wrote: > Hi Kanapriya, > > As explained in online, you have to set the relying party to the > authentication request. Basically, you have to test the CAS with federation > story that is available OOB, these are not a specific new scenario. > > *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/ha > rsha-thirimanna/10/ab8/122 > <http://wso2.com/signature> > > On Wed, Nov 2, 2016 at 12:16 PM, Malaka Silva wrote: > >> Hi Kanapriya, >> >> As we discussed can you further test the reason why federated >> authenticators >> are not supported. >> >> On Wed, Nov 2, 2016 at 10:38 AM, Malaka Silva wrote: >> >>> We can prioritize those use cases on demand. >>> >>> On Wed, Nov 2, 2016 at 10:32 AM, Kanapriya Kuleswararajan < >>> kanapr...@wso2.com> wrote: >>> >>>> Hi Harsha / Hasintha >>>> >>>> Basic authentication supports with the initial version of >>>> cas-inbound-authenticator. In next version of cas-inbound-authenticator, we >>>> can add federated support in future and while validating the tickets , we >>>> used /serviceValidate , not /samlValidate. >>>> >>>> As Kathees mentioned, there are other protocols (OpenID,OAuth and SAML) >>>> supports with CAS, but we didn't include that features in initial version >>>> of cas-inbound-authenticator. >>>> >>>> Thanks >>>> >>>> Kanapriya Kuleswararajan >>>> Associate Software Engineer >>>> Mobile : - 0774894438 >>>> Mail : - kanapr...@wso2.com >>>> >>>> On Wed, Nov 2, 2016 at 6:21 AM, Harsha Thirimanna >>>> wrote: >>>> >>>>> Hi Kanapriya, >>>>> >>>>> What Hasitha was asking about an issue with current implementation , >>>>> right ? I am not clear whether it is the problem here, >>>>> Hasitha , you gor solved the issue ? >>>>> >>>>> On Nov 1, 2016 11:57 PM, "Kathees Rajendram" wrote: >>>>> >>>>>> SAML-Protocol support is another feature in CAS. Please find few more >>>>>> resources for other protocols (OpenID,OAuth and SAML) supports as >>>>>> extensions in CAS protocol. >>>>>> >>>>>> https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.html >>>>>> https://apereo.github.io/cas/4.2.x/protocol/SAML-Protocol.html >>>>>> >>>>>> Thanks, >>>>>> Kathees >>>>>> >>>>>> On Tue, Nov 1, 2016 at 9:33 PM, Hasintha Indrajee >>>>>> wrote: >>>>>> >>>>>>> If this is the case then we should fix this in the sample cas client >>>>>>> webapp. >>>>>>> >>>>>>> On Tue, Nov 1, 2016 at 9:28 PM, Harsha Thirimanna >>>>>>> wrote: >>>>>>> >>>>>>>> So in your case, I feel like there should be missing the >>>>>>>> relyingParty value to pick the correct service provider to get the >>>>>>>> configured authentication options. >>>>>>>> >>>>>>>> *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/ha >>>>>>>> rsha-thirimanna/10/ab8/122 >>>>>>>> <http://wso2.com/signature> >>>>>>>> >>>>>>>> On Tue, Nov 1, 2016 at 9:15 PM, Hasintha Indrajee < >>>>>>>> hasin...
Re: [Dev] CAS connector doesnt work with federated authenticators.
yes, will check that Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Wed, Nov 2, 2016 at 12:16 PM, Malaka Silva wrote: > Hi Kanapriya, > > As we discussed can you further test the reason why federated > authenticators > are not supported. > > On Wed, Nov 2, 2016 at 10:38 AM, Malaka Silva wrote: > >> We can prioritize those use cases on demand. >> >> On Wed, Nov 2, 2016 at 10:32 AM, Kanapriya Kuleswararajan < >> kanapr...@wso2.com> wrote: >> >>> Hi Harsha / Hasintha >>> >>> Basic authentication supports with the initial version of >>> cas-inbound-authenticator. In next version of cas-inbound-authenticator, we >>> can add federated support in future and while validating the tickets , we >>> used /serviceValidate , not /samlValidate. >>> >>> As Kathees mentioned, there are other protocols (OpenID,OAuth and SAML) >>> supports with CAS, but we didn't include that features in initial version >>> of cas-inbound-authenticator. >>> >>> Thanks >>> >>> Kanapriya Kuleswararajan >>> Associate Software Engineer >>> Mobile : - 0774894438 >>> Mail : - kanapr...@wso2.com >>> >>> On Wed, Nov 2, 2016 at 6:21 AM, Harsha Thirimanna >>> wrote: >>> >>>> Hi Kanapriya, >>>> >>>> What Hasitha was asking about an issue with current implementation , >>>> right ? I am not clear whether it is the problem here, >>>> Hasitha , you gor solved the issue ? >>>> >>>> On Nov 1, 2016 11:57 PM, "Kathees Rajendram" wrote: >>>> >>>>> SAML-Protocol support is another feature in CAS. Please find few more >>>>> resources for other protocols (OpenID,OAuth and SAML) supports as >>>>> extensions in CAS protocol. >>>>> >>>>> https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.html >>>>> https://apereo.github.io/cas/4.2.x/protocol/SAML-Protocol.html >>>>> >>>>> Thanks, >>>>> Kathees >>>>> >>>>> On Tue, Nov 1, 2016 at 9:33 PM, Hasintha Indrajee >>>>> wrote: >>>>> >>>>>> If this is the case then we should fix this in the sample cas client >>>>>> webapp. >>>>>> >>>>>> On Tue, Nov 1, 2016 at 9:28 PM, Harsha Thirimanna >>>>>> wrote: >>>>>> >>>>>>> So in your case, I feel like there should be missing the >>>>>>> relyingParty value to pick the correct service provider to get the >>>>>>> configured authentication options. >>>>>>> >>>>>>> *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/ha >>>>>>> rsha-thirimanna/10/ab8/122 >>>>>>> <http://wso2.com/signature> >>>>>>> >>>>>>> On Tue, Nov 1, 2016 at 9:15 PM, Hasintha Indrajee >>>>>> > wrote: >>>>>>> >>>>>>>> Hi Harsha, >>>>>>>> >>>>>>>> Following are the resources you can get information about CAS >>>>>>>> (Provided by Kanapriya) >>>>>>>> >>>>>>>> https://docs.wso2.com/display/ISCONNECTORS/CAS+Inbound+Authe >>>>>>>> nticator >>>>>>>> https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/2 >>>>>>>> https://github.com/apereo/cas/blob/master/docs/cas-server-do >>>>>>>> cumentation/protocol/CAS-Protocol-Specification.md >>>>>>>> https://github.com/UniconLabs/cas-sample-java-webapp >>>>>>>> https://wiki.jasig.org/display/CASC/Configuring+the+Jasig+CA >>>>>>>> S+Client+for+Java+in+the+web.xml >>>>>>>> >>>>>>>> On Tue, Nov 1, 2016 at 7:56 PM, Harsha Thirimanna >>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi Hasintha, >>>>>>>>> >&g
Re: [Dev] CAS connector doesnt work with federated authenticators.
Hi Harsha / Hasintha Basic authentication supports with the initial version of cas-inbound-authenticator. In next version of cas-inbound-authenticator, we can add federated support in future and while validating the tickets , we used /serviceValidate , not /samlValidate. As Kathees mentioned, there are other protocols (OpenID,OAuth and SAML) supports with CAS, but we didn't include that features in initial version of cas-inbound-authenticator. Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Wed, Nov 2, 2016 at 6:21 AM, Harsha Thirimanna wrote: > Hi Kanapriya, > > What Hasitha was asking about an issue with current implementation , right > ? I am not clear whether it is the problem here, > Hasitha , you gor solved the issue ? > > On Nov 1, 2016 11:57 PM, "Kathees Rajendram" wrote: > >> SAML-Protocol support is another feature in CAS. Please find few more >> resources for other protocols (OpenID,OAuth and SAML) supports as >> extensions in CAS protocol. >> >> https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.html >> https://apereo.github.io/cas/4.2.x/protocol/SAML-Protocol.html >> >> Thanks, >> Kathees >> >> On Tue, Nov 1, 2016 at 9:33 PM, Hasintha Indrajee >> wrote: >> >>> If this is the case then we should fix this in the sample cas client >>> webapp. >>> >>> On Tue, Nov 1, 2016 at 9:28 PM, Harsha Thirimanna >>> wrote: >>> >>>> So in your case, I feel like there should be missing the relyingParty >>>> value to pick the correct service provider to get the configured >>>> authentication options. >>>> >>>> *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/ha >>>> rsha-thirimanna/10/ab8/122 >>>> <http://wso2.com/signature> >>>> >>>> On Tue, Nov 1, 2016 at 9:15 PM, Hasintha Indrajee >>>> wrote: >>>> >>>>> Hi Harsha, >>>>> >>>>> Following are the resources you can get information about CAS >>>>> (Provided by Kanapriya) >>>>> >>>>> https://docs.wso2.com/display/ISCONNECTORS/CAS+Inbound+Authenticator >>>>> https://github.com/wso2-extensions/identity-inbound-auth-cas/pull/2 >>>>> https://github.com/apereo/cas/blob/master/docs/cas-server-do >>>>> cumentation/protocol/CAS-Protocol-Specification.md >>>>> https://github.com/UniconLabs/cas-sample-java-webapp >>>>> https://wiki.jasig.org/display/CASC/Configuring+the+Jasig+CA >>>>> S+Client+for+Java+in+the+web.xml >>>>> >>>>> On Tue, Nov 1, 2016 at 7:56 PM, Harsha Thirimanna >>>>> wrote: >>>>> >>>>>> Hi Hasintha, >>>>>> >>>>>> Did you get any documentation for this to know the request and >>>>>> configuration details with CAS ? >>>>>> >>>>>> *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/ha >>>>>> rsha-thirimanna/10/ab8/122 >>>>>> <http://wso2.com/signature> >>>>>> >>>>>> On Tue, Nov 1, 2016 at 5:52 PM, Hasintha Indrajee >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I was trying to login through CAS as inbound protocol and I used >>>>>>> facebook as a federated authenticator. This scenario didn't work, It >>>>>>> always >>>>>>> prompt me Identity Server's basic auth login page. Aren't we supporting >>>>>>> this case ? Ideally we should support this right ?. Or am I missing >>>>>>> something here ? >>>>>>> >>>>>>> Also Do we have any idea to implement "samlValidate" in CAS near >>>>>>> future ? >>>>>>> >>>>>>> -- >>>>>>> Hasintha Indrajee >>>>>>> WSO2, Inc. >>>>>>> Mobile:+94 771892453 >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Hasintha Indrajee >>>>> WSO2, Inc. >>>>> Mobile:+94 771892453 >>>>> >>>>> >>>> >>> >>> >>> -- >>> Hasintha Indrajee >>> WSO2, Inc. >>> Mobile:+94 771892453 >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Kathees >> Software Engineer, >> email: kath...@wso2.com >> mobile: +94772596173 >> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How to get Inbound Authenticator Property Values
Hi All,
In outbound authenticators, we have set required properties in
authenticator UI as in [1] and get the values for that properties from the
authentication context as in [2]
[1]
List configProperties = new ArrayList<>();
Property apiKey = new Property();
apiKey.setName(Constants.APIKEY);
apiKey.setDisplayName(Constants.APIKEY);
apiKey.setRequired(true);
configProperties.add(apiKey);
[2]
Map authenticatorProperties = context.
getAuthenticatorProperties();
In Inbound authenticators also, we have set the UI properties as in [3].
Here we can get the value for acsUrl as in [4]
[3]
Property acsUrl = new Property();
acsUrl.setName(Constants.acsUrl);
acsUrl.setDisplayName(Constants.acsUrl);
return new Property[]{acsUrl};
[4]
for (InboundAuthenticationRequestConfig config : serviceProvider.
getInboundAuthenticationConfig().getInboundAuthenticationRequestConfigs()) {
String acsUrl = config.getInboundAuthKey();
}
Is this the way to get the property values whatever we set the value for
that property or Is there any other way to get those values like getting
the values from authentication context as in outbound authenticators.
Thanks
Kanapriya Kuleswararajan
Associate Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Need documentation for saml-cloud inbound authenticators
Hi All, I have tried [1] with wso2-is-5.2.0 and I got the following UI [2] for saml-cloud. But how can we get started with these inbound authenticator configurations or how can I test it with these inbound authenticators such as NetSuite,Amazon,Salesforce and etc. Is there any related documentation to follow up? [1] https://github.com/wso2-extensions/identity-inbound-auth-saml-cloud/tree/5.2.0-M1 [2] Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] wso2esb how to respond message in iso8583 inbound endpoint
Hi Alfario Eka Putra !
What I understand from your question is , You need to extract the field
id="105" from the response string
0210B2200210008056892300100500011056
32804568930005KAMAL021ABCDEFGHIJ 1234567890
If that so you can use the following piece of code to set the filed and
corresponding value
ISOMsg isoMsg = new ISOMsg();
isoMsg.setPackager(packager);
isoMsg.unpack(message.getBytes());
isoMsg.set("105", "xx 0");
byte[] msg = isoMsg.pack();
String packedMessage = new String(msg).toUpperCase();
isoMsg.dump(System.out, "");
return packedMessage;
Generally Inbound messages are inject into the sequence. For further
information, you can follow up the doc [1]. You can construct the format of
isomessage as you need by using payloadload factory mediator [2].
[1] https://docs.wso2.com/display/ESB490/Working+with+Inbound+Endpoints
[2] https://docs.wso2.com/display/ESB490/PayloadFactory+Mediator
Thanks
Kanapriya Kuleswararajan
Associate Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
On Thu, Sep 8, 2016 at 1:30 PM, Alfario Eka Putra wrote:
> I'm send ISO8583 message from testclient to my inbound,
>
> i have the log console :
>
>
> http://www.w3.org/2003/05/soap-envelope";>
>
> http://ws.apache.org/ns/synapse";>
>
> 0200
> 568893
> 0002
> 0110563280
> 456893
> DFGHT
> ABCDEFGHIJ 1234567890
>
>
>
>
>
>
> Response From Server :ISOMessage from pool-28-thread-1 is consumed :
> 0210B220021000805689230010050001105632804568930005KAMAL021ABCDEFGHIJ
> 1234567890
>
> how to change response from server, for example i want to change field id
> 105 from ABCDEFGHIJ 1234567890 to id="105">xx 0
>
> I don't know how to alter data and send it back to client. I search on
> wso2 documentation, how to respond message in inbound, but I can't find
> anything. how to handle incoming ISOMessage, alter it, and send it back to
> client? Do we need create connector or just simply modify data in sequence?
>
> thanks
>
> ___
> 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] WSO2 Committers += Rajjaz Mohammed
Congratz Rajjaz :) Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Mon, Jun 6, 2016 at 5:32 AM, Nifras Ismail wrote: > congratz Rajjaz!!! > > On Mon, Jun 6, 2016 at 6:33 AM, Kevin Ratnasekera wrote: > >> Congratulations Rajjaz ! >> >> On Mon, Jun 6, 2016 at 4:13 AM, Malaka Silva wrote: >> >>> Hi Devs, >>> >>> Its my pleasure to welcome Rajjaz Mohammed as a WSO2 Committer. >>> >>> He has been working with the WSO2 Platform Extensions Team and has >>> contributed immensely to ESB, IS and CEP product extensions, He is a very >>> dedicated and committed individual who is eager to learn. >>> >>> Rajjaz, welcome aboard and keep up the good work. >>> >>> >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Technical Lead >>> M: +94 777 219 791 >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> http://www.wso2.com/ >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> https://store.wso2.com/store/ >>> >>> Save a tree -Conserve nature & Save the world for your future. Print >>> this email only if it is absolutely necessary. >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Kevin Ratnaskera* >> Software Engineer >> WSO2 Inc. - http://wso2.com >> lean . enterprise . middleware >> Mobile - +94774696950 >> Linkedin - https://www.linkedin.com/in/djkevincr >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Nifras Ismail > Associate Software Engineer > WSO2 > Email : nif...@wso2.com > Mobile : 0094 77 89 90 300 > > ___ > 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] Error while login the database using sqlplus
Hi malaka , I tried with above comment and reinstall the software also . I couldn't figure it out the reason for the error. As discussed in the meeting , For the timing, I tried it with windows , I can start up the instance of the oracle database successfully . I will continue the remaining installation and the configuration with windows machine. Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Thu, Jun 2, 2016 at 6:05 PM, Malaka Silva wrote: > Check the following comment. > > *finally, I switch the system user from root to oracle. And I login > success*. > > [1] > http://stackoverflow.com/questions/16043193/ora-12547-tns-lost-contact-when-running-dbca-on-oracle-11g-installation-on-ubun > > On Thu, Jun 2, 2016 at 5:20 PM, Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> HI Malaka ! >> >> I already tried with above discussion, and now also double check with >> that , but I get the same error. >> >> Thanks >> >> Kanapriya Kuleswararajan >> Associate Software Engineer >> Mobile : - 0774894438 >> Mail : - kanapr...@wso2.com >> >> On Thu, Jun 2, 2016 at 5:02 PM, Malaka Silva wrote: >> >>> Did you already checked the following discussion? >>> >>> >>> http://www.dadbm.com/how-to-fix-ora-12547-tns-lost-contact-when-try-to-connect-to-oracle/ >>> >>> On Thu, Jun 2, 2016 at 4:22 PM, Kanapriya Kuleswararajan < >>> kanapr...@wso2.com> wrote: >>> >>>> Hi all, >>>> >>>> I'm following [1] to install and configure oracle Oracle Identity and >>>> Access Management. >>>> Before install the identity and access management , need to install >>>> oracle database and follow the installation guide [2] for install the >>>> database. >>>> >>>> I successfully install the oracle software and create the oracle >>>> database . >>>> But When I try to login with oracle database with sqlplus, I'm getting >>>> following error [3] . >>>> >>>> Note: I have add the necessary kernal parameters and necessary >>>> dependencies packages as well. >>>> >>>> In bash_profile , I set the ORACLE_HOME,ORACLE_SID and ORACLE_BASE as >>>> following. >>>> >>>> ORACLE_UNQNAME=oracleDa; export ORACLE_UNQNAME >>>> ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE >>>> ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_6; export ORACLE_HOME >>>> ORACLE_SID=oracleDa; export ORACLE_SID >>>> PATH=/usr/sbin:$PATH; export PATH >>>> PATH=$ORACLE_HOME/bin:$PATH; export PATH >>>> >>>> [1] >>>> https://docs.oracle.com/cd/E23520_01/doc.311/e20664/chapter_12.htm#autoId0 >>>> [2] >>>> https://docs.oracle.com/cd/E27559_01/install.1112/e27301/install.htm#INOAM75795 >>>> [3] >>>> >>>> >>>> Anyone faced this kind of error? What could be the reason ? >>>> >>>> >>>> >>>> Kanapriya Kuleswararajan >>>> Associate Software Engineer >>>> Mobile : - 0774894438 >>>> Mail : - kanapr...@wso2.com >>>> >>>> >>> >>> >>> >>> -- >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Tech Lead >>> M: +94 777 219 791 >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> http://www.wso2.com/ >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> https://store.wso2.com/store/ >>> >>> Save a tree -Conserve nature & Save the world for your future. Print >>> this email only if it is absolutely necessary. >>> >> >> > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while login the database using sqlplus
HI Malaka ! I already tried with above discussion, and now also double check with that , but I get the same error. Thanks Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com On Thu, Jun 2, 2016 at 5:02 PM, Malaka Silva wrote: > Did you already checked the following discussion? > > > http://www.dadbm.com/how-to-fix-ora-12547-tns-lost-contact-when-try-to-connect-to-oracle/ > > On Thu, Jun 2, 2016 at 4:22 PM, Kanapriya Kuleswararajan < > kanapr...@wso2.com> wrote: > >> Hi all, >> >> I'm following [1] to install and configure oracle Oracle Identity and >> Access Management. >> Before install the identity and access management , need to install >> oracle database and follow the installation guide [2] for install the >> database. >> >> I successfully install the oracle software and create the oracle database >> . >> But When I try to login with oracle database with sqlplus, I'm getting >> following error [3] . >> >> Note: I have add the necessary kernal parameters and necessary >> dependencies packages as well. >> >> In bash_profile , I set the ORACLE_HOME,ORACLE_SID and ORACLE_BASE as >> following. >> >> ORACLE_UNQNAME=oracleDa; export ORACLE_UNQNAME >> ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE >> ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_6; export ORACLE_HOME >> ORACLE_SID=oracleDa; export ORACLE_SID >> PATH=/usr/sbin:$PATH; export PATH >> PATH=$ORACLE_HOME/bin:$PATH; export PATH >> >> [1] >> https://docs.oracle.com/cd/E23520_01/doc.311/e20664/chapter_12.htm#autoId0 >> [2] >> https://docs.oracle.com/cd/E27559_01/install.1112/e27301/install.htm#INOAM75795 >> [3] >> >> >> Anyone faced this kind of error? What could be the reason ? >> >> >> >> Kanapriya Kuleswararajan >> Associate Software Engineer >> Mobile : - 0774894438 >> Mail : - kanapr...@wso2.com >> >> > > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while login the database using sqlplus
Hi all, I'm following [1] to install and configure oracle Oracle Identity and Access Management. Before install the identity and access management , need to install oracle database and follow the installation guide [2] for install the database. I successfully install the oracle software and create the oracle database . But When I try to login with oracle database with sqlplus, I'm getting following error [3] . Note: I have add the necessary kernal parameters and necessary dependencies packages as well. In bash_profile , I set the ORACLE_HOME,ORACLE_SID and ORACLE_BASE as following. ORACLE_UNQNAME=oracleDa; export ORACLE_UNQNAME ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_6; export ORACLE_HOME ORACLE_SID=oracleDa; export ORACLE_SID PATH=/usr/sbin:$PATH; export PATH PATH=$ORACLE_HOME/bin:$PATH; export PATH [1] https://docs.oracle.com/cd/E23520_01/doc.311/e20664/chapter_12.htm#autoId0 [2] https://docs.oracle.com/cd/E27559_01/install.1112/e27301/install.htm#INOAM75795 [3] Anyone faced this kind of error? What could be the reason ? Kanapriya Kuleswararajan Associate Software Engineer Mobile : - 0774894438 Mail : - kanapr...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while run the integrationTest amazonSNS
Hi Kesavan,
As you mentioned , I replaced the keystore folder its works fine.
Thanks
Kanapriya Kuleswararajan
Associate Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
On Mon, Feb 22, 2016 at 2:26 PM, Kesavan Yogarajah
wrote:
> Hi Kanapriya,
>
> It seems that empty keystore in the test folder causes this problem.
> Please replace the keystore and try.
>
> Thanks
>
> Kesavan Yogarajah
> Associate Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> On Mon, Feb 22, 2016 at 1:49 PM, Kanapriya Kuleswararajan <
> kanapr...@wso2.com> wrote:
>
>> Hi all,
>> I got the following error when I tried to run the intergrationTest of
>> amazonsns connector.
>>
>> FYI :- Manual testing works fine.
>>
>>
>> ---
>> T E S T S
>> ---
>> Running TestSuite
>> [2016-02-22 13:24:07,472] INFO
>> {org.wso2.carbon.automation.core.PlatformExecutionManager} -
>> ---Test Execution Started --
>> [2016-02-22 13:24:07,481] INFO
>> {org.wso2.carbon.automation.core.ServerGroupManager} - Carbon zip file -
>> /home/kanapriya/Desktop/NEWESBCONNECTORS-CLONE1-14-01-2016/copy_clone_feb_7_/esb-connectors/amazonsns/amazonsns-connector/amazonsns-connector-1.0.0/org.wso2.carbon.connector/../../../../repository/wso2esb-4.9.0.zip
>> [2016-02-22 13:24:11,390] INFO
>> {org.wso2.carbon.automation.core.ServerGroupManager} - Copying
>> /home/kanapriya/Desktop/NEWESBCONNECTORS-CLONE1-14-01-2016/copy_clone_feb_7_/esb-connectors/amazonsns/amazonsns-connector/amazonsns-connector-1.0.0/org.wso2.carbon.connector/target/security-verifier/SecVerifier.aar
>> =>
>> /home/kanapriya/Desktop/NEWESBCONNECTORS-CLONE1-14-01-2016/copy_clone_feb_7_/esb-connectors/amazonsns/amazonsns-connector/amazonsns-connector-1.0.0/org.wso2.carbon.connector/target/carbontmp1456127647489/wso2esb-4.9.0/repository/deployment/server/axis2services/SecVerifier.aar
>> [2016-02-22 13:24:11,476] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils} -
>> Instrumentation of jar files in progress ...
>> [2016-02-22 13:24:17,502] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.CodeCoverageUtils} -
>> Instrumented 80 files.
>> [2016-02-22 13:24:17,502] INFO
>> {org.wso2.carbon.automation.core.utils.serverutils.ServerUtils} - Starting
>> server.
>> [2016-02-22 13:24:17,571] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> JAVA_HOME environment variable is set to /usr/local/java/jdk1.7.0_79
>> [2016-02-22 13:24:17,571] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> CARBON_HOME environment variable is set to
>> /home/kanapriya/Desktop/NEWESBCONNECTORS-CLONE1-14-01-2016/copy_clone_feb_7_/esb-connectors/amazonsns/amazonsns-connector/amazonsns-connector-1.0.0/org.wso2.carbon.connector/target/carbontmp1456127647489/wso2esb-4.9.0
>> [2016-02-22 13:24:21,540] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,539] INFO - CarbonCoreActivator Starting WSO2
>> Carbon...
>> [2016-02-22 13:24:21,543] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,543] INFO - CarbonCoreActivator Operating System :
>> Linux 3.13.0-77-generic, amd64
>> [2016-02-22 13:24:21,543] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,543] INFO - CarbonCoreActivator Java Home:
>> /usr/local/java/jdk1.7.0_79/jre
>> [2016-02-22 13:24:21,543] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,543] INFO - CarbonCoreActivator Java Version :
>> 1.7.0_79
>> [2016-02-22 13:24:21,543] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,543] INFO - CarbonCoreActivator Java VM :
>> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
>> [2016-02-22 13:24:21,543] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-02-22 13:24:21,543] INFO - CarbonCoreActivator Carbon Home :
>> /home/kanapriya/Desktop/NEWESBCONNECTORS-CLONE1-14-01-2016/copy_clone_feb_7_/esb-connectors/amazonsns/amazonsns-connector/amazonsns-connector-1.0.0/org.wso2.carbon.connector/target/carbontmp1456127647489/wso2esb-4.9.0
>> [2016-02-22 13:2
[Dev] Error while run the integrationTest amazonSNS
.2.0/org.wso2.carbon.registry.uddi-4.2.0.jar
[2016-02-22 13:24:46,017] INFO
{org.apache.axis2.deployment.ModuleDeployer} - Deploying module:
uddiversionmodule-4.2.0 -
file:/home/kanapriya/.m2/repository/org/wso2/carbon/org.wso2.carbon.registry.uddi/4.2.0/org.wso2.carbon.registry.uddi-4.2.0.jar
[2016-02-22 13:24:46,019] INFO
{org.apache.axis2.deployment.ModuleDeployer} - Deploying module:
pagination-4.2.0 -
file:/home/kanapriya/.m2/repository/org/wso2/carbon/org.wso2.carbon.registry.server/4.2.0/org.wso2.carbon.registry.server-4.2.0.jar
[2016-02-22 13:24:46,019] INFO
{org.apache.axis2.deployment.ModuleDeployer} - Deploying module:
pagination-4.2.0 -
file:/home/kanapriya/.m2/repository/org/wso2/carbon/org.wso2.carbon.registry.server/4.2.0/org.wso2.carbon.registry.server-4.2.0.jar
[2016-02-22 13:24:46,031] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,031] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,031] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
[2016-02-22 13:24:46,031] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
[2016-02-22 13:24:46,032] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,032] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,032] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
[2016-02-22 13:24:46,032] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
[2016-02-22 13:24:46,033] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,033] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - I/O exception
(java.net.SocketException) caught when processing request:
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)
[2016-02-22 13:24:46,033] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
[2016-02-22 13:24:46,033] INFO
{org.apache.commons.httpclient.HttpMethodDirector} - Retrying request
Can anyone guide me on this ?
Thanks
Kanapriya Kuleswararajan
Associate Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
