Re: [Dev] Orbit update for Paho-MQTT Library

[Kalpa Welivitigoda]

Hi Eranda,

Do we have an update on this? If $subject is not needed anymore please
close [1].

On Fri, Mar 13, 2015 at 9:59 AM, Kishanthan Thangarajah  wrote:

> Did you go through the checklist of items for orbit creation process?
> There is a doc on this.
>
> On Mon, Mar 9, 2015 at 6:03 PM, Eranda Rajapakshe 
> wrote:
>
>> Hi,
>>
>> Please review the pull request [1].
>>
>> [1]. *https://github.com/wso2/orbit/pull/67
>> *
>>
>> Thank you!
>> --
>> *Eranda Rajapakshe*
>> Software Engineering intern
>> WSO2 Inc. www.wso2.com
>> Tel : +94784822608
>> Email : eran...@wso2.com
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][IS] slf4j version conflict with 1.6.x and 1.7.x

[Ayyoob Hamza]

Hi All,

In CDMF, When we install DAS feature with along the IS (4.6.0-M2) features.
Then we found IS features doesn't get activated. When we track the issue we
were able find that IS depends on slf4j version from 1.6.0 to 1.7.0 and DAS
depends on version from 1.7.0 to 1.8.0 Further we have both the slf4j
1.7.10 and 1.6.1 libraries within our pack. Yet only slf4j 1.7.10 gets
activated. The reason for this problem was:

slf4j 1.6.1 imports a package "org.slf4j.impl" and when slf4j 1.7.10 and
1.6.1 both has been used on the same product, then on slf4j- version 1.6.1
imports ("org.slf4j.impl" ) gets wired with 1.7.10 because the version has
been given as a single value rather a range.  Due to this it doesn't get
activated. Therefore we have to increase the range of slf4j from
[1.6.1,1.7) to [1.6.1,1.8) . The change wont have any effect because [1],
slf4j is compatible between 1.6.x and 1.7.x

Therefore I believe we have to only depend on latest slf4j version. where
having both causes the problem on wiring. So I think we have to update the
slf4j version on IS. This will arise a problem where IS dependent library
also needs to use the slf4j 1.7 range.

If there is any other solution please let know.

[1] http://www.slf4j.org/manual.html

Thanks
*Ayyoob Hamza*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Chanuka Dissanayake

[Johann Nallathamby]

Hi All,

It's my pleasure to announce Chanuka Dissanayake as a WSO2 Committer.
Chanuka has been a valuable contributor for WSO2 Identity Server product,
and in recognition of his contribution to WSO2, he has been voted as a WSO2
Committer.

Chanuka, congratulations and keep up the good work!

Thanks & Regards.

-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "[DEV] [IS] [oauth2] Error occurred for custom grant type

[Pushpalanka Jayawardhana]

Hi Kavitha,

Please replace the existing setAuthorized(String str) method as per below
code. We have changed it to be like setAuthorized(User user) now.

if (username.indexOf(CarbonConstants.DOMAIN_SEPARATOR) < 0 &&
UserCoreUtil.getDomainFromThreadLocal()
!= null && !"".equals(UserCoreUtil.getDomainFromThreadLocal())) { username =
UserCoreUtil.getDomainFromThreadLocal() + CarbonConstants.DOMAIN_SEPARATOR +
username; } tokReqMsgCtx.setAuthorizedUser(OAuth2Util.
getUserFromUserName(username));

[1] -
https://github.com/wso2/carbon-identity/blob/master/components/oauth/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/handlers/grant/PasswordGrantHandler.java#L114-#L120

Thanks,
Pushpalanka.
-- 
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka


On Mon, Sep 28, 2015 at 3:46 PM, Kavitha Subramaniyam 
wrote:

> Hi IS team,
>
> I'm getting an error[1] for Oauth2 custom grant type when generating
> access token for grant type-mobile in IS-5.1.0-Alpha and I have noticed
> that there is a resolved jira[2] says that "..fix provides support to add
> custom grant types by allowing to add grant type validators..". I have been
> added custom type following below steps.
> Appreciate if you can look into this issue and clarify for me?
>
> Steps:
> - altered identity.xml by including
> 
> mobile
>
> org.soasecurity.is.oauth.grant.mobile.MobileGrant
>
> org.soasecurity.is.oauth.grant.mobile.MobileGrantValidator
> 
>
> - copied .jar into /repository/components/lib
>  (accessed .jar, MobileGrant and MobileGrantValidator from here:
> https://svn.wso2.org/repos/wso2/people/asela/oauth/custom-grant/)
> - Start server and Created oauth app (here cuss)
> - execute below curl with relavant client_id:client_secret
>
> $ curl --user VmmZNaIRJ0U3Iz_Tanh6uH3go2ga:_yIJQ5lLVfQ_XylSguwE05rDjBYa -k
> -d "grant_type=mobile&mobileNumber=0333444" -H "Content-Type:
> application/x-www-form-urlencoded" https://localhost:9443/oauth2/token
>
> [2] https://wso2.org/jira/browse/IDENTITY-2925
> [1]
> --
>
> [2015-09-28 14:13:31,916] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  Received a request : /oauth2/token
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  --logging request headers.--
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  authorization : Basic
> Vm1tWk5hSVJKMFUzSXpfVGFuaDZ1SDNnbzJnYTpfeUlKUTVsTFZmUV9YeWxTZ3V3RTA1ckRqQllh
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  user-agent : curl/7.35.0
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  host
> : localhost:9443
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  accept : */*
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  content-type : application/x-www-form-urlencoded;charset=UTF-8
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  content-length : 38
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  --logging request parameters.--
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  grant_type - mobile
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  client_id - null
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  code
> - null
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  redirect_uri - null
> [2015-09-28 14:13:31,929] DEBUG
> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Access Token request
> received for Client ID VmmZNaIRJ0U3Iz_Tanh6uH3go2ga, User ID null, Scope :
> [] and Grant Type : mobile
> [2015-09-28 14:13:31,931] DEBUG
> {org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
> -  Can authenticate with client ID and Secret. Client ID:
> VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
> [2015-09-28 14:13:31,932] DEBUG
> {org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
> -  Grant type : mobile Strict client validation set to : null
> [2015-09-28 14:13:31,933] DEBUG
> {org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Client credentials
> were available in the cache for client id : VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
> [2015-09-28 14:13:31,934] DEBUG
> {org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Successfully
> authenticated the client w

[Dev] [IS] SMS OTP Authenticator

[Malaka Silva]

Hi All,

We are currently implementing the $subject.

I think we can user [1] and [2] for testing.

Is there are any better ways of doing it? Good idea for an ESB connector as
well?

[1] http://opensmpp.org/
[2] https://adywicaksono.wordpress.com/2007/07/11/smpp-server-simulator/

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/


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] UES build failure after updating to identity 4.6.0.alpha

[Udara Rathnayake]

Hi Maduranga,

Please have a look at Identity Provider Server Feature[1] as well. As a
temporary workaround to get UES m3 out we have added following to one of
our features(which is wrong). P.lease update this thread once you release
beta with relevant fixes.
Created jira[2]

org.slf4j:slf4j-log4j12
org.slf4j:slf4j-api
net.sf.ehcache.wso2:ehcache

[1]
Cannot complete the install because one or more required items could not be
found.
 Software being installed: Identity Provider Server Feature 4.6.0.alpha
(org.wso2.carbon.identity.provider.server.feature.group 4.6.0.alpha)
 Missing requirement: openid4java 1.0.0.wso2v1 (openid4java 1.0.0.wso2v1)
requires 'package net.sf.ehcache [1.5.0,1.6.0)' but it could not be found
 Cannot satisfy dependency:
  From: Identity Provider Server Feature 4.6.0.alpha
(org.wso2.carbon.identity.provider.server.feature.group 4.6.0.alpha)
  To: openid4java [1.0.0.wso2v1]
Application failed, log file location:
/tmp/m2-ues2/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443504549355.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 User Engagement Server ... SUCCESS [0.913s]
[INFO] UES Server - UI styles  SUCCESS [1.275s]
[INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS [0.025s]
[INFO] WSO2 Carbon - UES feature . SUCCESS [0.580s]
[INFO] UES - Profile Generation .. FAILURE [11.781s]
[INFO] WSO2 User Engagement Server - Distribution  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 15.412s
[INFO] Finished at: Tue Sep 29 10:59:13 IST 2015
[INFO] Final Memory: 23M/329M
[INFO]


[2] https://wso2.org/jira/browse/IDENTITY-3672


On Mon, Sep 28, 2015 at 7:21 PM, Maduranga Siriwardena 
wrote:

> Hi Udara,
>
> We are planing to release carbon-identity beta 15th of October.
>
> Thanks,
> Maduranga
>
> On Mon, Sep 28, 2015 at 7:18 PM, Udara Rathnayake  wrote:
>
>> Hi Maduraga,
>>
>> When are you planning to do the 4.6.0 beta release?
>>
>> On Mon, Sep 28, 2015 at 3:21 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Udara,
>>>
>>> We have created a new orbit bundle for oltu (which is previously known
>>> as amber) to remove forked amber repository. oltu is packed from OAuth
>>> feature and seems like this feature installation causes issues due to the
>>> absence of slf4j new version. We haven't encountered any issues with this
>>> feature installation since we pack this version of slf4j from some other
>>> features.  We will pack it from Oauth feature in carbon-identity beta
>>> release.
>>>
>>> Meanwhile if you are packing slf4j, can please upgrade your slf4j
>>> version to 1.6.1.
>>>
>>> Thanks,
>>> Maduranga
>>>
>>> On Mon, Sep 28, 2015 at 1:36 PM, Udara Rathnayake 
>>> wrote:
>>>
 Hi Identity team,

 Getting following build failure. Any idea about this?
 Do we need to add org.slf4j as a dependency?

 Software being installed: OAuth Feature 4.6.0.alpha
 (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
  Missing requirement: oltu 1.0.0.wso2v1 (oltu 1.0.0.wso2v1) requires
 'package org.slf4j [1.6.1,1.7.0)' but it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - OAuth Common 4.6.0.alpha
 (org.wso2.carbon.identity.oauth.common 4.6.0.alpha)
   To: package org.apache.oltu.oauth2.common.validators [1.0.0,1.1.0)
  Cannot satisfy dependency:
   From: Identity OAuth Common Feature 4.6.0.alpha
 (org.wso2.carbon.identity.oauth.common.feature.group 4.6.0.alpha)
   To: org.wso2.carbon.identity.oauth.common [4.6.0.alpha]
  Cannot satisfy dependency:
   From: OAuth Feature 4.6.0.alpha
 (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
   To: org.wso2.carbon.identity.oauth.common.feature.group [4.6.0.alpha]
 Application failed, log file location:
 /tmp/m2-ues/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443427357769.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 User Engagement Server ... SUCCESS
 [0.831s]
 [INFO] UES Server - UI styles  SUCCESS
 [1.259s]
 [INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS
 [0.038s]
 [INFO] WSO2 Carbon - UES feature . SUCCESS
 [0.570s]
 [INFO] UES - Profile Generation .. FAILURE
 [11.531s]
 [INFO] WSO2 User Engagement Server - Distribution  SKIPPED
 [INFO]
 ---

Re: [Dev] [UES] Reading request parameters of dashboard page URL inside widget and publish it

[Manuranga Perera]

thanks Thanuja.

On Tue, Sep 29, 2015 at 10:39 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Manuranga,
>
> I have create a jira [1] to track this issue and attached the local
> modification I've done.
>
> Thanks.
>
> [1]. https://wso2.org/jira/browse/UES-582
>
> On Tue, Sep 29, 2015 at 10:00 AM, Manuranga Perera  wrote:
>
>> we don't have a jira for this. please create one and attach the local
>> modification you have.
>>
>> On Tue, Sep 29, 2015 at 9:59 AM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi Manuranga, Lalanke,
>>>
>>> As we discussed offline, currently Lalanke is doing some implementation
>>> to publish data from dashboard to gadget using pub-sub model and with the
>>> help of Lalanke I was able to patch locally DAS analytics dashboard to use
>>> above mentioned feature. Thanks a lot for the help Manurnga and Lalanke.
>>> Could you please point out the Jira issue to track this?
>>>
>>> Thanks.
>>>
>>> On Wed, Sep 16, 2015 at 9:34 AM, Manuranga Perera  wrote:
>>>
 Hi Thanuja,
 Way are you trying to pass the URL parameters? can you please explain
 what you trying to implement. and please give us a example of the 
 parameter.

 On Tue, Sep 15, 2015 at 10:27 PM, Thanuja Uruththirakodeeswaran <
 thanu...@wso2.com> wrote:

> Hi Manuranga,
>
> I have a widget and gadget in my dashboard page. The widget is to
> filter some values and then gadget will display the filtered data using 
> the
> publisher-subscriber model.
> When I'm navigating to the dashboard page from my main page, I'm
> passing some params in the URL. I want to read those request param from 
> the
> page URL and publish those values to the gadget.
> I'm using '*parent.window.location' *to read the request params
> inside the widget and publishing that value to subscriber gadget.
> Lalanke said it's not a good way and suggested to get help from you.
> Also if I follow this approach and once the values are read from url, I 
> try
> to publish the values and got *'Uncaught Error:
> OpenAjax.hub.Error.Disconnected*' error.
> So what is the best way to read request params and publish it?
>
> Thanks.
>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com

>>>
>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UES] Reading request parameters of dashboard page URL inside widget and publish it

[Thanuja Uruththirakodeeswaran]

Hi Manuranga,

I have create a jira [1] to track this issue and attached the local
modification I've done.

Thanks.

[1]. https://wso2.org/jira/browse/UES-582

On Tue, Sep 29, 2015 at 10:00 AM, Manuranga Perera  wrote:

> we don't have a jira for this. please create one and attach the local
> modification you have.
>
> On Tue, Sep 29, 2015 at 9:59 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Manuranga, Lalanke,
>>
>> As we discussed offline, currently Lalanke is doing some implementation
>> to publish data from dashboard to gadget using pub-sub model and with the
>> help of Lalanke I was able to patch locally DAS analytics dashboard to use
>> above mentioned feature. Thanks a lot for the help Manurnga and Lalanke.
>> Could you please point out the Jira issue to track this?
>>
>> Thanks.
>>
>> On Wed, Sep 16, 2015 at 9:34 AM, Manuranga Perera  wrote:
>>
>>> Hi Thanuja,
>>> Way are you trying to pass the URL parameters? can you please explain
>>> what you trying to implement. and please give us a example of the parameter.
>>>
>>> On Tue, Sep 15, 2015 at 10:27 PM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi Manuranga,

 I have a widget and gadget in my dashboard page. The widget is to
 filter some values and then gadget will display the filtered data using the
 publisher-subscriber model.
 When I'm navigating to the dashboard page from my main page, I'm
 passing some params in the URL. I want to read those request param from the
 page URL and publish those values to the gadget.
 I'm using '*parent.window.location' *to read the request params inside
 the widget and publishing that value to subscriber gadget.
 Lalanke said it's not a good way and suggested to get help from you.
 Also if I follow this approach and once the values are read from url, I try
 to publish the values and got *'Uncaught Error:
 OpenAjax.hub.Error.Disconnected*' error.
 So what is the best way to read request params and publish it?

 Thanks.



 --
 Thanuja Uruththirakodeeswaran
 Software Engineer
 WSO2 Inc.;http://wso2.com
 lean.enterprise.middleware

 mobile: +94 774363167

>>>
>>>
>>>
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] WSO2 DAS + BRS

[Imesh Gunaratne]

[+ WSO2 Dev]

Hi Marco,

May be you have not copied the Private PaaS membership scheme bundle to the
lib folder. Please refer below:
https://github.com/wso2/product-private-paas/tree/master/extensions/carbon/ppaas-membership-scheme

Thanks

On Tue, Sep 29, 2015 at 1:23 AM, Monaco Marco  wrote:

> Hi Imesh,
>
> i'm still having problems with DAS. If I use the cartridge as in the
> sample (default profile with 2 instances) I receive this error:
>
> TID: [-1234] [] [2015-09-28 19:50:57,674]  WARN
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> localMemberHost is configured to use the loopback address. Hazelcast
> Clustering needs ip addresses for localMemberHost and well-known members.
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2015-09-28 19:50:57,674] ERROR
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Invalid membership scheme 'private-paas'. Supported schemes are multicast,
> wka & aws
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2015-09-28 19:50:57,675] ERROR
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -  Cannot
> initialize cluster
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent}
> org.apache.axis2.clustering.ClusteringFault: Invalid membership scheme
> 'private-paas'. Supported schemes are multicast, wka & aws
> at
> org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.getMembershipScheme(HazelcastClusteringAgent.java:423)
> at
> org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.configureMembershipScheme(HazelcastClusteringAgent.java:376)
> at
> org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent.init(HazelcastClusteringAgent.java:150)
> at
> org.wso2.carbon.core.util.ClusteringUtil.enableClustering(ClusteringUtil.java:38)
> at
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:177)
> at
> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:288)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous

Re: [Dev] [UES] Reading request parameters of dashboard page URL inside widget and publish it

[Manuranga Perera]

we don't have a jira for this. please create one and attach the local
modification you have.

On Tue, Sep 29, 2015 at 9:59 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Manuranga, Lalanke,
>
> As we discussed offline, currently Lalanke is doing some implementation to
> publish data from dashboard to gadget using pub-sub model and with the help
> of Lalanke I was able to patch locally DAS analytics dashboard to use above
> mentioned feature. Thanks a lot for the help Manurnga and Lalanke. Could
> you please point out the Jira issue to track this?
>
> Thanks.
>
> On Wed, Sep 16, 2015 at 9:34 AM, Manuranga Perera  wrote:
>
>> Hi Thanuja,
>> Way are you trying to pass the URL parameters? can you please explain
>> what you trying to implement. and please give us a example of the parameter.
>>
>> On Tue, Sep 15, 2015 at 10:27 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi Manuranga,
>>>
>>> I have a widget and gadget in my dashboard page. The widget is to filter
>>> some values and then gadget will display the filtered data using the
>>> publisher-subscriber model.
>>> When I'm navigating to the dashboard page from my main page, I'm passing
>>> some params in the URL. I want to read those request param from the page
>>> URL and publish those values to the gadget.
>>> I'm using '*parent.window.location' *to read the request params inside
>>> the widget and publishing that value to subscriber gadget.
>>> Lalanke said it's not a good way and suggested to get help from you.
>>> Also if I follow this approach and once the values are read from url, I try
>>> to publish the values and got *'Uncaught Error:
>>> OpenAjax.hub.Error.Disconnected*' error.
>>> So what is the best way to read request params and publish it?
>>>
>>> Thanks.
>>>
>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>
>>
>>
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UES] Reading request parameters of dashboard page URL inside widget and publish it

[Thanuja Uruththirakodeeswaran]

Hi Manuranga, Lalanke,

As we discussed offline, currently Lalanke is doing some implementation to
publish data from dashboard to gadget using pub-sub model and with the help
of Lalanke I was able to patch locally DAS analytics dashboard to use above
mentioned feature. Thanks a lot for the help Manurnga and Lalanke. Could
you please point out the Jira issue to track this?

Thanks.

On Wed, Sep 16, 2015 at 9:34 AM, Manuranga Perera  wrote:

> Hi Thanuja,
> Way are you trying to pass the URL parameters? can you please explain what
> you trying to implement. and please give us a example of the parameter.
>
> On Tue, Sep 15, 2015 at 10:27 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Manuranga,
>>
>> I have a widget and gadget in my dashboard page. The widget is to filter
>> some values and then gadget will display the filtered data using the
>> publisher-subscriber model.
>> When I'm navigating to the dashboard page from my main page, I'm passing
>> some params in the URL. I want to read those request param from the page
>> URL and publish those values to the gadget.
>> I'm using '*parent.window.location' *to read the request params inside
>> the widget and publishing that value to subscriber gadget.
>> Lalanke said it's not a good way and suggested to get help from you. Also
>> if I follow this approach and once the values are read from url, I try to
>> publish the values and got *'Uncaught Error:
>> OpenAjax.hub.Error.Disconnected*' error.
>> So what is the best way to read request params and publish it?
>>
>> Thanks.
>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] "[DEV] [IS] [oauth2] Error occurred for custom grant type

[Lakshman Udayakantha]

Hi Kavitha,

problem here is NoSuchMethodError exception. The reason for this exception
is when you build the jars that method (in your case setAuthorizedUser) is
available in to the compiling environment. but when your jar is in run
time, that method is not available.

If I extend the lakshani's statement, initially OAuthTokenReqMessageContext
class has setAuthorizedUser method that accept string argument.but later
this method has changed to take User object as argument. Well my guess is,
This happens because in OAuthTokenReqMessageContext in old jar provided by
asela, has taken string argument, but in runtime environment available in
IS 5.1.0 alpha pack has taken User object argument in the same jar.

To make this scenario work, you have to recompile the source in [1] with
dependencies in latest pack. old jar has compiled with oauth 4.2.3 jar. As
I can see in alpha pack they are using carbon identity version as 4.6.0-M2. you
have to recompile the the source with that dependency version. you will
need to refectories that method (setAuthorizedUser) also.

[1] https://svn.wso2.org/repos/wso2/people/asela/oauth/custom-grant/

Thanks

On Mon, Sep 28, 2015 at 8:56 PM, Lakshani Gamage  wrote:

> Hi Kavitha,
>
> As you can see in [1], setAuthorizedUser is taking a User object but not a
> String.
>
> [1]
> https://github.com/wso2/carbon-identity/blob/3dbd2ad3c3271943d289e2535bfb7e7bb896ba80/components/oauth/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/OAuthTokenReqMessageContext.java
>
> Thanks,
> Lakshani
>
> On Mon, Sep 28, 2015 at 3:46 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi IS team,
>>
>> I'm getting an error[1] for Oauth2 custom grant type when generating
>> access token for grant type-mobile in IS-5.1.0-Alpha and I have noticed
>> that there is a resolved jira[2] says that "..fix provides support to add
>> custom grant types by allowing to add grant type validators..". I have been
>> added custom type following below steps.
>> Appreciate if you can look into this issue and clarify for me?
>>
>> Steps:
>> - altered identity.xml by including
>> 
>> mobile
>>
>> org.soasecurity.is.oauth.grant.mobile.MobileGrant
>>
>> org.soasecurity.is.oauth.grant.mobile.MobileGrantValidator
>> 
>>
>> - copied .jar into /repository/components/lib
>>  (accessed .jar, MobileGrant and MobileGrantValidator from here:
>> https://svn.wso2.org/repos/wso2/people/asela/oauth/custom-grant/)
>> - Start server and Created oauth app (here cuss)
>> - execute below curl with relavant client_id:client_secret
>>
>> $ curl --user VmmZNaIRJ0U3Iz_Tanh6uH3go2ga:_yIJQ5lLVfQ_XylSguwE05rDjBYa
>> -k -d "grant_type=mobile&mobileNumber=0333444" -H "Content-Type:
>> application/x-www-form-urlencoded" https://localhost:9443/oauth2/token
>>
>> [2] https://wso2.org/jira/browse/IDENTITY-2925
>> [1]
>> --
>>
>> [2015-09-28 14:13:31,916] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  Received a request : /oauth2/token
>> [2015-09-28 14:13:31,917] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  --logging request headers.--
>> [2015-09-28 14:13:31,917] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  authorization : Basic
>> Vm1tWk5hSVJKMFUzSXpfVGFuaDZ1SDNnbzJnYTpfeUlKUTVsTFZmUV9YeWxTZ3V3RTA1ckRqQllh
>> [2015-09-28 14:13:31,917] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  user-agent : curl/7.35.0
>> [2015-09-28 14:13:31,917] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  host
>> : localhost:9443
>> [2015-09-28 14:13:31,917] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  accept : */*
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  content-type : application/x-www-form-urlencoded;charset=UTF-8
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  content-length : 38
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  --logging request parameters.--
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  grant_type - mobile
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  client_id - null
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  code
>> - null
>> [2015-09-28 14:13:31,918] DEBUG
>> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>>  redirect_uri - null
>> [2015-09-28 14:13:31,929] DEBUG
>> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Access Token request
>> received for Client ID VmmZNaIRJ0U3Iz_Tanh6uH3go2ga, User ID null, Scope :
>> [] and Grant Type : mobile
>> [2015-09-28 14:13:31,931]

Re: [Dev] [IS] OAuth Authentication Error

[Lakshani Gamage]

Hi Sachith,

Please do a remote debug with correct identity component version, and find
out which object is null here. That will be helpful to find the issue.

Thanks,
Lakshani

On Mon, Sep 28, 2015 at 5:10 AM, Sachith Punchihewa 
wrote:

> Hi IS Team,
>
> I have a custom OAuth authenticator installed.It works as intended when a
> invalid  token is passed as the access token.
> But when the request contains a valid  access token a null point exception
> occurs from " *validateScope*" method in "*DefaultOAuth2TokenValidator*".
> Any reason for this behavior ?
> Error, log, incoming request and code snippet is given below.
>
> *Code Snippet from the Authenticator Class:*
>
> OAuth2TokenValidationRequestDTO oauthValidationRequest = new
>> OAuth2TokenValidationRequestDTO();
>
> // create access token object to validate and populate it
>
> OAuth2TokenValidationRequestDTO.OAuth2AccessToken oAuth2AccessToken =
>> oauthValidationRequest
>
> .new OAuth2AccessToken();
>
>
>> oAuth2AccessToken.setTokenType(OauthAuthenticatorConstants.BEARER_TOKEN_TYPE);
>
> oAuth2AccessToken.setIdentifier(accessToken);
>
> //set the token to the validation request
>
> oauthValidationRequest.setAccessToken(oAuth2AccessToken);
>
> OAuth2TokenValidationService oauthValidationService = new
>> OAuth2TokenValidationService();
>
> OAuth2ClientApplicationDTO oauthValidationResponse = oauthValidationService
>
> .findOAuthConsumerIfTokenIsValid(oauthValidationRequest);
>
> return
>> oauthValidationResponse.getAccessTokenValidationResponse().isValid();
>
>
>
> *Incoming Request Maker Code Snippit :*
>
>
>>
>>
>>
>>
>>
>>
>> *var headers = [{name : "Authorization", value : "Bearer
>> bf90ee34984d69e661e7770631a95f0"}];var userStoreRespond = new
>> ws.WSRequest();var options = new Array();options.HTTPHeaders =
>> headers;options.useSOAP = 1.2;options.useWSA = 1.0;options.action =
>> "urn:getSecondaryRealmConfigurations";*
>>
>> *var payload = '>  xmlns:xsd="http://org.apache.axis2/xsd " />';*
>> var result;
>> try {
>>
>> *userStoreRespond.open(options,
>> "https://10.100.7.102:9443/services/UserStoreConfigAdminService.UserStoreConfigAdminServiceHttpsSoap12Endpoint/
>> ",
>> false); userStoreRespond.send(payload);*
>> result = userStoreRespond.responseE4X;
>> } catch (e) {
>> log.error(e.toString());
>> }
>
>
> *Error Log:*
>
>>
>> [2015-09-28 11:12:39,831] ERROR
>> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.identity.oauth2.validators.DefaultOAuth2TokenValidator.validateScope(DefaultOAuth2TokenValidator.java:52)
>> at
>> org.wso2.carbon.identity.oauth2.validators.TokenValidationHandler.findOAuthConsumerIfTokenIsValid(TokenValidationHandler.java:245)
>> at
>> org.wso2.carbon.identity.oauth2.OAuth2TokenValidationService.findOAuthConsumerIfTokenIsValid(OAuth2TokenValidationService.java:65)
>> at
>> org.wso2.mdm.oauth.extension.OauthAuthenticator.isAuthenticated(OauthAuthenticator.java:74)
>> at
>> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:187)
>> at
>> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:96)
>> at
>> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicatio

Re: [Dev] "[DEV] [IS] [oauth2] Error occurred for custom grant type

[Lakshani Gamage]

Hi Kavitha,

As you can see in [1], setAuthorizedUser is taking a User object but not a
String.

[1]
https://github.com/wso2/carbon-identity/blob/3dbd2ad3c3271943d289e2535bfb7e7bb896ba80/components/oauth/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/OAuthTokenReqMessageContext.java

Thanks,
Lakshani

On Mon, Sep 28, 2015 at 3:46 PM, Kavitha Subramaniyam 
wrote:

> Hi IS team,
>
> I'm getting an error[1] for Oauth2 custom grant type when generating
> access token for grant type-mobile in IS-5.1.0-Alpha and I have noticed
> that there is a resolved jira[2] says that "..fix provides support to add
> custom grant types by allowing to add grant type validators..". I have been
> added custom type following below steps.
> Appreciate if you can look into this issue and clarify for me?
>
> Steps:
> - altered identity.xml by including
> 
> mobile
>
> org.soasecurity.is.oauth.grant.mobile.MobileGrant
>
> org.soasecurity.is.oauth.grant.mobile.MobileGrantValidator
> 
>
> - copied .jar into /repository/components/lib
>  (accessed .jar, MobileGrant and MobileGrantValidator from here:
> https://svn.wso2.org/repos/wso2/people/asela/oauth/custom-grant/)
> - Start server and Created oauth app (here cuss)
> - execute below curl with relavant client_id:client_secret
>
> $ curl --user VmmZNaIRJ0U3Iz_Tanh6uH3go2ga:_yIJQ5lLVfQ_XylSguwE05rDjBYa -k
> -d "grant_type=mobile&mobileNumber=0333444" -H "Content-Type:
> application/x-www-form-urlencoded" https://localhost:9443/oauth2/token
>
> [2] https://wso2.org/jira/browse/IDENTITY-2925
> [1]
> --
>
> [2015-09-28 14:13:31,916] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  Received a request : /oauth2/token
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  --logging request headers.--
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  authorization : Basic
> Vm1tWk5hSVJKMFUzSXpfVGFuaDZ1SDNnbzJnYTpfeUlKUTVsTFZmUV9YeWxTZ3V3RTA1ckRqQllh
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  user-agent : curl/7.35.0
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  host
> : localhost:9443
> [2015-09-28 14:13:31,917] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  accept : */*
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  content-type : application/x-www-form-urlencoded;charset=UTF-8
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  content-length : 38
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  --logging request parameters.--
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  grant_type - mobile
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  client_id - null
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  code
> - null
> [2015-09-28 14:13:31,918] DEBUG
> {org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
>  redirect_uri - null
> [2015-09-28 14:13:31,929] DEBUG
> {org.wso2.carbon.identity.oauth2.OAuth2Service} -  Access Token request
> received for Client ID VmmZNaIRJ0U3Iz_Tanh6uH3go2ga, User ID null, Scope :
> [] and Grant Type : mobile
> [2015-09-28 14:13:31,931] DEBUG
> {org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
> -  Can authenticate with client ID and Secret. Client ID:
> VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
> [2015-09-28 14:13:31,932] DEBUG
> {org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
> -  Grant type : mobile Strict client validation set to : null
> [2015-09-28 14:13:31,933] DEBUG
> {org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Client credentials
> were available in the cache for client id : VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
> [2015-09-28 14:13:31,934] DEBUG
> {org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Successfully
> authenticated the client with client id : VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
> [2015-09-28 14:13:31,935]  INFO
> {org.soasecurity.is.oauth.grant.mobile.MobileGrant} -  Mobile Grant handler
> is hit
> [2015-09-28 14:13:31,942] ERROR
> {org.apache.catalina.core.StandardWrapperValve} -  Servlet.service() for
> servlet [OAuth2Endpoints] in context with path [/oauth2] threw exception
> java.lang.RuntimeException: org.apache.cxf.interceptor.Fault:
> org.wso2.carbon.identity.oauth2.token.OAuthTokenReqMessageContext.setAuthorizedUser(Ljava/lang/String;)V
> at
> org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainIniti

Re: [Dev] UES build failure after updating to identity 4.6.0.alpha

[Maduranga Siriwardena]

Hi Udara,

We are planing to release carbon-identity beta 15th of October.

Thanks,
Maduranga

On Mon, Sep 28, 2015 at 7:18 PM, Udara Rathnayake  wrote:

> Hi Maduraga,
>
> When are you planning to do the 4.6.0 beta release?
>
> On Mon, Sep 28, 2015 at 3:21 PM, Maduranga Siriwardena  > wrote:
>
>> Hi Udara,
>>
>> We have created a new orbit bundle for oltu (which is previously known as
>> amber) to remove forked amber repository. oltu is packed from OAuth feature
>> and seems like this feature installation causes issues due to the absence
>> of slf4j new version. We haven't encountered any issues with this feature
>> installation since we pack this version of slf4j from some other features.
>> We will pack it from Oauth feature in carbon-identity beta release.
>>
>> Meanwhile if you are packing slf4j, can please upgrade your slf4j version
>> to 1.6.1.
>>
>> Thanks,
>> Maduranga
>>
>> On Mon, Sep 28, 2015 at 1:36 PM, Udara Rathnayake 
>> wrote:
>>
>>> Hi Identity team,
>>>
>>> Getting following build failure. Any idea about this?
>>> Do we need to add org.slf4j as a dependency?
>>>
>>> Software being installed: OAuth Feature 4.6.0.alpha
>>> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>>>  Missing requirement: oltu 1.0.0.wso2v1 (oltu 1.0.0.wso2v1) requires
>>> 'package org.slf4j [1.6.1,1.7.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - OAuth Common 4.6.0.alpha
>>> (org.wso2.carbon.identity.oauth.common 4.6.0.alpha)
>>>   To: package org.apache.oltu.oauth2.common.validators [1.0.0,1.1.0)
>>>  Cannot satisfy dependency:
>>>   From: Identity OAuth Common Feature 4.6.0.alpha
>>> (org.wso2.carbon.identity.oauth.common.feature.group 4.6.0.alpha)
>>>   To: org.wso2.carbon.identity.oauth.common [4.6.0.alpha]
>>>  Cannot satisfy dependency:
>>>   From: OAuth Feature 4.6.0.alpha
>>> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>>>   To: org.wso2.carbon.identity.oauth.common.feature.group [4.6.0.alpha]
>>> Application failed, log file location:
>>> /tmp/m2-ues/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443427357769.log
>>>
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] WSO2 User Engagement Server ... SUCCESS
>>> [0.831s]
>>> [INFO] UES Server - UI styles  SUCCESS
>>> [1.259s]
>>> [INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS
>>> [0.038s]
>>> [INFO] WSO2 Carbon - UES feature . SUCCESS
>>> [0.570s]
>>> [INFO] UES - Profile Generation .. FAILURE
>>> [11.531s]
>>> [INFO] WSO2 User Engagement Server - Distribution  SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 15.019s
>>> [INFO] Finished at: Mon Sep 28 13:32:41 IST 2015
>>> [INFO] Final Memory: 23M/329M
>>>
>>> Regards,
>>> UdaraR
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Maduranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>> email: madura...@wso2.com
>> mobile: +94718990591
>>
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] UES build failure after updating to identity 4.6.0.alpha

[Udara Rathnayake]

Hi Maduraga,

When are you planning to do the 4.6.0 beta release?

On Mon, Sep 28, 2015 at 3:21 PM, Maduranga Siriwardena 
wrote:

> Hi Udara,
>
> We have created a new orbit bundle for oltu (which is previously known as
> amber) to remove forked amber repository. oltu is packed from OAuth feature
> and seems like this feature installation causes issues due to the absence
> of slf4j new version. We haven't encountered any issues with this feature
> installation since we pack this version of slf4j from some other features.
> We will pack it from Oauth feature in carbon-identity beta release.
>
> Meanwhile if you are packing slf4j, can please upgrade your slf4j version
> to 1.6.1.
>
> Thanks,
> Maduranga
>
> On Mon, Sep 28, 2015 at 1:36 PM, Udara Rathnayake  wrote:
>
>> Hi Identity team,
>>
>> Getting following build failure. Any idea about this?
>> Do we need to add org.slf4j as a dependency?
>>
>> Software being installed: OAuth Feature 4.6.0.alpha
>> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>>  Missing requirement: oltu 1.0.0.wso2v1 (oltu 1.0.0.wso2v1) requires
>> 'package org.slf4j [1.6.1,1.7.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - OAuth Common 4.6.0.alpha
>> (org.wso2.carbon.identity.oauth.common 4.6.0.alpha)
>>   To: package org.apache.oltu.oauth2.common.validators [1.0.0,1.1.0)
>>  Cannot satisfy dependency:
>>   From: Identity OAuth Common Feature 4.6.0.alpha
>> (org.wso2.carbon.identity.oauth.common.feature.group 4.6.0.alpha)
>>   To: org.wso2.carbon.identity.oauth.common [4.6.0.alpha]
>>  Cannot satisfy dependency:
>>   From: OAuth Feature 4.6.0.alpha
>> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>>   To: org.wso2.carbon.identity.oauth.common.feature.group [4.6.0.alpha]
>> Application failed, log file location:
>> /tmp/m2-ues/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443427357769.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 User Engagement Server ... SUCCESS
>> [0.831s]
>> [INFO] UES Server - UI styles  SUCCESS
>> [1.259s]
>> [INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS
>> [0.038s]
>> [INFO] WSO2 Carbon - UES feature . SUCCESS
>> [0.570s]
>> [INFO] UES - Profile Generation .. FAILURE
>> [11.531s]
>> [INFO] WSO2 User Engagement Server - Distribution  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 15.019s
>> [INFO] Finished at: Mon Sep 28 13:32:41 IST 2015
>> [INFO] Final Memory: 23M/329M
>>
>> Regards,
>> UdaraR
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> email: madura...@wso2.com
> mobile: +94718990591
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Rajeenthini Satkunam]

Hi all,

Thank you for your prompt reply.I have done this from uesAutomationContext.
getConfigurationValue("//maximumWaitingTime") and Now I can get the value
for maximumWaitingTime.

On Mon, Sep 28, 2015 at 2:20 PM, Pumudu Ruhunage  wrote:

> Hi,
>
> Have you tried something like this?
>
> AutomationContext automationContext;
> automationContext = new AutomationContext();
> String maximumWaitingTime =
> automationContext.getInstance().getProperty("maximumWaitingTime");
>
> It's better if you can check how other integration tests were written and
> follow the same pattern to refer automation.xml. (without creating new
> automationContext and use already initialized objects etc.)
>
> Regards,
> Pumudu
>
> On Mon, Sep 28, 2015 at 2:05 PM, Mushthaq Rumy  wrote:
>
>> Hi Rajeenthani,
>>
>> I think you need to create an object instance of AutomationContext within
>> your java class and proceed with it. The below link[1] might be useful for
>> you.
>>
>> [1]
>> http://malinthas.blogspot.com/2014/02/how-to-obtain-configuration-details.html
>> .
>>
>>
>>
>> On Mon, Sep 28, 2015 at 1:44 PM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I am currently working on writing UI integration tests for product UES
>>> using selenium.I have to make maximum waiting time for search element by()
>>> as default value.As per discussion it can be configured through
>>> automation.xml file. I have added 30>> maximumWaitingTime> at automation.xml file.So I need to get the value
>>> of it for test java classes.Can anyone please give any suggestion on how to
>>> get that value?
>>>
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823>   *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> Thanks & Regards,
>> --
>> Mushthaq Rumy
>> *Software Engineer*
>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>> Email : musht...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Pumudu Ruhunage
> Associate Software Engineer | WSO2 Inc
> M: +94 779 664493  | http://wso2.com
>



-- 

*Thank You.*

*Rajeenthini Satkunam*

*Associate Software Engineer | WSO2*


*E:rajeenth...@wso2.com *

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

Re: [Dev] [AF] Error while creating a version for existing application.

[Amalka Subasinghe]

Hi Kasun,

I applied the given fix and tested this scenario, still I'm getting the
same exception. This need to investigate more and give a proper solution.

Thanks
Amalka

On Mon, Sep 28, 2015 at 12:40 PM, Amalka Subasinghe  wrote:

> I will try this fix and update soon
>
> On Thu, Sep 24, 2015 at 3:01 PM, Kasun De Silva  wrote:
>
>> Hi Amalka,
>>
>> According to the registry team this could be possibly fix with the
>> following change into the RxtManager. Is this intermittent?  Can you
>> reproduce this regularly? This should be reproducible in our local setups
>> right? Is so please patch the appfactory.core with the diff provided, and
>> test. Let us know the results.
>>
>> diff --git
>> a/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
>> b/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
>> index 3259299..609419d 100644
>> ---
>> a/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
>> +++
>> b/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
>> @@ -200,6 +200,7 @@ public class RxtManager {
>>  factory.setProperty(XMLInputFactory.IS_COALESCING, true);
>>  XMLStreamReader reader = null;
>>  reader = factory.createXMLStreamReader(new
>> StringReader(info));
>> +   GovernanceUtils.loadGovernanceArtifacts(userRegistry);
>>  GenericArtifactManager manager = new
>> GenericArtifactManager(userRegistry, key);
>>  GenericArtifact artifact = manager.newGovernanceArtifact(new
>> StAXOMBuilder(reader).getDocumentElement());
>>
>>
>> Thanks,
>> Kasun
>>
>>
>> *Kasun de Silva*
>> Software Engineer | *WSO2 Inc.*; http://wso2.com
>> lean.enterprise.middleware
>>
>> email   : kas...@wso2.com
>> mobile : +94 77 794 4260
>>
>>
>> On Tue, Sep 15, 2015 at 2:08 PM, Amalka Subasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>>
>>> I got the following error, when I try to create a version in an existing
>>> application
>>>
>>> By referring the logs, we can see that config and governance registries
>>> are being loaded.
>>>
>>> TID: [0] [AF] [2015-09-15 01:06:23,476]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>>> to mount at config in 5ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>>
>>> TID: [0] [AF] [2015-09-15 01:06:23,619]  INFO
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>>> to mount at governance in 12ms
>>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>>
>>>
>>> however, after I login to the carbon console, using the same tenant I
>>> could create the version without errors.
>>>
>>>
>>> TID: [0] [AF] [2015-09-14 21:02:41,818] ERROR
>>> {org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl}
>>> -  Error in associating lifecycle for the artifact. id:
>>> e47109a2-893b-4c7d-a76a-1fc46aa25954, path:
>>> /repository/applications/aftestsetupmonitori/1.0.0.
>>> {org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl}
>>>
>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Couldn't
>>> find aspectName 'ApplicationLifecycle'
>>>
>>>at
>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.associateAspect(EmbeddedRegistry.java:2428)
>>>
>>>at
>>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.associateAspect(CacheBackedRegistry.java:416)
>>>
>>>at
>>> org.wso2.carbon.registry.core.session.UserRegistry.associateAspectInternal(UserRegistry.java:1904)
>>>
>>>at
>>> org.wso2.carbon.registry.core.session.UserRegistry.access$3800(UserRegistry.java:60)
>>>
>>>at
>>> org.wso2.carbon.registry.core.session.UserRegistry$39.run(UserRegistry.java:1876)
>>>
>>>at
>>> org.wso2.carbon.registry.core.session.UserRegistry$39.run(UserRegistry.java:1873)
>>>
>>>at java.security.AccessController.doPrivileged(Native Method)
>>>
>>>at
>>> org.wso2.carbon.registry.core.session.UserRegistry.associateAspect(UserRegistry.java:1873)
>>>
>>>at
>>> org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.attachLifecycle(GovernanceArtifactImpl.java:276)
>>>at
>>> org.wso2.carbon.appfactory.core.governance.RxtManager.addArtifact(RxtManager.java:212)
>>>
>>>
>>> Thanks
>>> Amalka
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Amalka Subasinghe
> Senior Software Engineer
> WSO2 Inc.
> Mobile: +94 77 9401267
>



-- 
Amalka Subasinghe
Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] "[DEV] [IS] [oauth2] Error occurred for custom grant type

[Kavitha Subramaniyam]

Hi IS team,

I'm getting an error[1] for Oauth2 custom grant type when generating access
token for grant type-mobile in IS-5.1.0-Alpha and I have noticed that there
is a resolved jira[2] says that "..fix provides support to add custom grant
types by allowing to add grant type validators..". I have been added custom
type following below steps.
Appreciate if you can look into this issue and clarify for me?

Steps:
- altered identity.xml by including

mobile

org.soasecurity.is.oauth.grant.mobile.MobileGrant

org.soasecurity.is.oauth.grant.mobile.MobileGrantValidator


- copied .jar into /repository/components/lib
 (accessed .jar, MobileGrant and MobileGrantValidator from here:
https://svn.wso2.org/repos/wso2/people/asela/oauth/custom-grant/)
- Start server and Created oauth app (here cuss)
- execute below curl with relavant client_id:client_secret

$ curl --user VmmZNaIRJ0U3Iz_Tanh6uH3go2ga:_yIJQ5lLVfQ_XylSguwE05rDjBYa -k
-d "grant_type=mobile&mobileNumber=0333444" -H "Content-Type:
application/x-www-form-urlencoded" https://localhost:9443/oauth2/token

[2] https://wso2.org/jira/browse/IDENTITY-2925
[1]
--

[2015-09-28 14:13:31,916] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 Received a request : /oauth2/token
[2015-09-28 14:13:31,917] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 --logging request headers.--
[2015-09-28 14:13:31,917] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 authorization : Basic
Vm1tWk5hSVJKMFUzSXpfVGFuaDZ1SDNnbzJnYTpfeUlKUTVsTFZmUV9YeWxTZ3V3RTA1ckRqQllh
[2015-09-28 14:13:31,917] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 user-agent : curl/7.35.0
[2015-09-28 14:13:31,917] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  host
: localhost:9443
[2015-09-28 14:13:31,917] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 accept : */*
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 content-type : application/x-www-form-urlencoded;charset=UTF-8
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 content-length : 38
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 --logging request parameters.--
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 grant_type - mobile
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 client_id - null
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -  code
- null
[2015-09-28 14:13:31,918] DEBUG
{org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint} -
 redirect_uri - null
[2015-09-28 14:13:31,929] DEBUG
{org.wso2.carbon.identity.oauth2.OAuth2Service} -  Access Token request
received for Client ID VmmZNaIRJ0U3Iz_Tanh6uH3go2ga, User ID null, Scope :
[] and Grant Type : mobile
[2015-09-28 14:13:31,931] DEBUG
{org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
-  Can authenticate with client ID and Secret. Client ID:
VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
[2015-09-28 14:13:31,932] DEBUG
{org.wso2.carbon.identity.oauth2.token.handlers.clientauth.AbstractClientAuthHandler}
-  Grant type : mobile Strict client validation set to : null
[2015-09-28 14:13:31,933] DEBUG
{org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Client credentials
were available in the cache for client id : VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
[2015-09-28 14:13:31,934] DEBUG
{org.wso2.carbon.identity.oauth2.util.OAuth2Util} -  Successfully
authenticated the client with client id : VmmZNaIRJ0U3Iz_Tanh6uH3go2ga
[2015-09-28 14:13:31,935]  INFO
{org.soasecurity.is.oauth.grant.mobile.MobileGrant} -  Mobile Grant handler
is hit
[2015-09-28 14:13:31,942] ERROR
{org.apache.catalina.core.StandardWrapperValve} -  Servlet.service() for
servlet [OAuth2Endpoints] in context with path [/oauth2] threw exception
java.lang.RuntimeException: org.apache.cxf.interceptor.Fault:
org.wso2.carbon.identity.oauth2.token.OAuthTokenReqMessageContext.setAuthorizedUser(Ljava/lang/String;)V
at
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:116)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:331)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.ap

Re: [Dev] UES build failure after updating to identity 4.6.0.alpha

[Maduranga Siriwardena]

Hi Udara,

We have created a new orbit bundle for oltu (which is previously known as
amber) to remove forked amber repository. oltu is packed from OAuth feature
and seems like this feature installation causes issues due to the absence
of slf4j new version. We haven't encountered any issues with this feature
installation since we pack this version of slf4j from some other features.
We will pack it from Oauth feature in carbon-identity beta release.

Meanwhile if you are packing slf4j, can please upgrade your slf4j version
to 1.6.1.

Thanks,
Maduranga

On Mon, Sep 28, 2015 at 1:36 PM, Udara Rathnayake  wrote:

> Hi Identity team,
>
> Getting following build failure. Any idea about this?
> Do we need to add org.slf4j as a dependency?
>
> Software being installed: OAuth Feature 4.6.0.alpha
> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>  Missing requirement: oltu 1.0.0.wso2v1 (oltu 1.0.0.wso2v1) requires
> 'package org.slf4j [1.6.1,1.7.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - OAuth Common 4.6.0.alpha
> (org.wso2.carbon.identity.oauth.common 4.6.0.alpha)
>   To: package org.apache.oltu.oauth2.common.validators [1.0.0,1.1.0)
>  Cannot satisfy dependency:
>   From: Identity OAuth Common Feature 4.6.0.alpha
> (org.wso2.carbon.identity.oauth.common.feature.group 4.6.0.alpha)
>   To: org.wso2.carbon.identity.oauth.common [4.6.0.alpha]
>  Cannot satisfy dependency:
>   From: OAuth Feature 4.6.0.alpha
> (org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
>   To: org.wso2.carbon.identity.oauth.common.feature.group [4.6.0.alpha]
> Application failed, log file location:
> /tmp/m2-ues/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443427357769.log
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 User Engagement Server ... SUCCESS [0.831s]
> [INFO] UES Server - UI styles  SUCCESS [1.259s]
> [INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS
> [0.038s]
> [INFO] WSO2 Carbon - UES feature . SUCCESS [0.570s]
> [INFO] UES - Profile Generation .. FAILURE
> [11.531s]
> [INFO] WSO2 User Engagement Server - Distribution  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 15.019s
> [INFO] Finished at: Mon Sep 28 13:32:41 IST 2015
> [INFO] Final Memory: 23M/329M
>
> Regards,
> UdaraR
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing Google Spread Sheet Connector

[Rajjaz Mohammed]

Hi thulasika,
in Spreadsheet Connector OAuth is implemented for 2.0 but some methods
still requesting in OAuth 1 flow so Try to change the Requesting Mechanism..

On Mon, Sep 28, 2015 at 3:03 PM, Thulasika Vijayanathan 
wrote:

> Hi Malaka,
>
> yes, I can do this.
>
> Thanks,
>
> On Mon, Sep 28, 2015 at 2:48 PM, Malaka Silva  wrote:
>
>> Hi Thulasika,
>>
>> As discussed offline can you start on this please?
>>
>> On Wed, Sep 23, 2015 at 2:16 PM, Madusanka Premaratne <
>> madusan...@wso2.com> wrote:
>>
>>> The real reason to worry about Google Plus Connector is MySelf +
>>> TharinduA developed it as one of our training work sometimes back.
>>> Anyway thanks for the response.
>>>
>>> Madusanka
>>>
>>> On Wed, Sep 23, 2015 at 2:10 PM, Malaka Silva  wrote:
>>>
 Yes we have done some of those and will do in future as well.

 We will not be doing google plus since it not widely used anymore.

 On Wed, Sep 23, 2015 at 1:55 PM, Madusanka Premaratne <
 madusan...@wso2.com> wrote:

> Hi Malaka,
> AFAIK most of the google APIs got changed with that particular update
> mentioned by Rajjaz. We might need to change GooglePlus and other Google
> connectors also.
>
> Thanks,
> Madusanka
>
> On Wed, Sep 23, 2015 at 11:12 AM, Rajjaz Mohammed 
> wrote:
>
>> +1
>> some methods(Create Spreadsheet) are still not changed to OAuth 2.0
>> so there are not working.  since Spreadsheet one of important Connector
>> better if we can rewrite quickly.
>>
>> On Wed, Sep 23, 2015 at 10:44 AM, Malaka Silva 
>> wrote:
>>
>>> Hi,
>>>
>>> We will be removing this connector, since the api this connector was
>>> written is deprecated by google. Only some of the methods are currently
>>> working.
>>>
>>> Will add a new version soon.
>>>
>>> https://store.wso2.com/store/
>>>
>>> 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/
>>> 
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Thank you
>> Best Regards
>>
>> *Rajjaz HM*
>> Associate Software Engineer
>> WSO2 Inc. 
>> lean | enterprise | middleware
>> Mobile | +94752833834
>> Email   | raj...@wso2.com
>> LinkedIn | Blogger | WSO2 Profile
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image:
> Twitter]  [image: Google Plus]
>  
> [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


 --

 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/
 

 Save a tree -Conserve nature & Save the world for your future. Print
 this email only if it is absolutely necessary.

>>>
>>>
>>>
>>> --
>>> *Madusanka Premaratne* | Associate Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>>> Email: madusan...@wso2.com | Web: www.wso2.com
>>>
>>> [image: Facebook]  [image: Twitter]
>>>  [image: Google Plus]
>>>  [image:
>>> Linkedin]  [image: Instagram]
>>> 

Re: [Dev] Removing Google Spread Sheet Connector

[Thulasika Vijayanathan]

Hi Malaka,

yes, I can do this.

Thanks,

On Mon, Sep 28, 2015 at 2:48 PM, Malaka Silva  wrote:

> Hi Thulasika,
>
> As discussed offline can you start on this please?
>
> On Wed, Sep 23, 2015 at 2:16 PM, Madusanka Premaratne  > wrote:
>
>> The real reason to worry about Google Plus Connector is MySelf +
>> TharinduA developed it as one of our training work sometimes back.
>> Anyway thanks for the response.
>>
>> Madusanka
>>
>> On Wed, Sep 23, 2015 at 2:10 PM, Malaka Silva  wrote:
>>
>>> Yes we have done some of those and will do in future as well.
>>>
>>> We will not be doing google plus since it not widely used anymore.
>>>
>>> On Wed, Sep 23, 2015 at 1:55 PM, Madusanka Premaratne <
>>> madusan...@wso2.com> wrote:
>>>
 Hi Malaka,
 AFAIK most of the google APIs got changed with that particular update
 mentioned by Rajjaz. We might need to change GooglePlus and other Google
 connectors also.

 Thanks,
 Madusanka

 On Wed, Sep 23, 2015 at 11:12 AM, Rajjaz Mohammed 
 wrote:

> +1
> some methods(Create Spreadsheet) are still not changed to OAuth 2.0 so
> there are not working.  since Spreadsheet one of important Connector 
> better
> if we can rewrite quickly.
>
> On Wed, Sep 23, 2015 at 10:44 AM, Malaka Silva 
> wrote:
>
>> Hi,
>>
>> We will be removing this connector, since the api this connector was
>> written is deprecated by google. Only some of the methods are currently
>> working.
>>
>> Will add a new version soon.
>>
>> https://store.wso2.com/store/
>>
>> 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/
>> 
>>
>> Save a tree -Conserve nature & Save the world for your future. Print
>> this email only if it is absolutely necessary.
>>
>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Madusanka Premaratne* | Associate Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 835 70 73| Work: +94 112 145 345
 Email: madusan...@wso2.com | Web: www.wso2.com

 [image: Facebook]  [image: Twitter]
  [image: Google Plus]
  [image:
 Linkedin]  [image: Instagram]
  [image: Skype]
 


>>>
>>>
>>> --
>>>
>>> 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/
>>> 
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
>
> 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.co

Re: [Dev] Removing Google Spread Sheet Connector

[Malaka Silva]

Hi Thulasika,

As discussed offline can you start on this please?

On Wed, Sep 23, 2015 at 2:16 PM, Madusanka Premaratne 
wrote:

> The real reason to worry about Google Plus Connector is MySelf + TharinduA
> developed it as one of our training work sometimes back.
> Anyway thanks for the response.
>
> Madusanka
>
> On Wed, Sep 23, 2015 at 2:10 PM, Malaka Silva  wrote:
>
>> Yes we have done some of those and will do in future as well.
>>
>> We will not be doing google plus since it not widely used anymore.
>>
>> On Wed, Sep 23, 2015 at 1:55 PM, Madusanka Premaratne <
>> madusan...@wso2.com> wrote:
>>
>>> Hi Malaka,
>>> AFAIK most of the google APIs got changed with that particular update
>>> mentioned by Rajjaz. We might need to change GooglePlus and other Google
>>> connectors also.
>>>
>>> Thanks,
>>> Madusanka
>>>
>>> On Wed, Sep 23, 2015 at 11:12 AM, Rajjaz Mohammed 
>>> wrote:
>>>
 +1
 some methods(Create Spreadsheet) are still not changed to OAuth 2.0 so
 there are not working.  since Spreadsheet one of important Connector better
 if we can rewrite quickly.

 On Wed, Sep 23, 2015 at 10:44 AM, Malaka Silva  wrote:

> Hi,
>
> We will be removing this connector, since the api this connector was
> written is deprecated by google. Only some of the methods are currently
> working.
>
> Will add a new version soon.
>
> https://store.wso2.com/store/
>
> 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/
> 
>
> Save a tree -Conserve nature & Save the world for your future. Print
> this email only if it is absolutely necessary.
>



 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 WSO2 Inc. 
 lean | enterprise | middleware
 Mobile | +94752833834
 Email   | raj...@wso2.com
 LinkedIn | Blogger | WSO2 Profile
 

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


>>>
>>>
>>> --
>>> *Madusanka Premaratne* | Associate Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>>> Email: madusan...@wso2.com | Web: www.wso2.com
>>>
>>> [image: Facebook]  [image: Twitter]
>>>  [image: Google Plus]
>>>  [image:
>>> Linkedin]  [image: Instagram]
>>>  [image: Skype]
>>> 
>>>
>>>
>>
>>
>> --
>>
>> 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/
>> 
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


-- 

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/


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://ws

[Dev] [IS] OAuth Authentication Error

[Sachith Punchihewa]

Hi IS Team,

I have a custom OAuth authenticator installed.It works as intended when a
invalid  token is passed as the access token.
But when the request contains a valid  access token a null point exception
occurs from " *validateScope*" method in "*DefaultOAuth2TokenValidator*".
Any reason for this behavior ?
Error, log, incoming request and code snippet is given below.

*Code Snippet from the Authenticator Class:*

OAuth2TokenValidationRequestDTO oauthValidationRequest = new
> OAuth2TokenValidationRequestDTO();

// create access token object to validate and populate it

OAuth2TokenValidationRequestDTO.OAuth2AccessToken oAuth2AccessToken =
> oauthValidationRequest

.new OAuth2AccessToken();

oAuth2AccessToken.setTokenType(OauthAuthenticatorConstants.BEARER_TOKEN_TYPE);

oAuth2AccessToken.setIdentifier(accessToken);

//set the token to the validation request

oauthValidationRequest.setAccessToken(oAuth2AccessToken);

OAuth2TokenValidationService oauthValidationService = new
> OAuth2TokenValidationService();

OAuth2ClientApplicationDTO oauthValidationResponse = oauthValidationService

.findOAuthConsumerIfTokenIsValid(oauthValidationRequest);

return oauthValidationResponse.getAccessTokenValidationResponse().isValid();



*Incoming Request Maker Code Snippit :*


>
>
>
>
>
>
> *var headers = [{name : "Authorization", value : "Bearer
> bf90ee34984d69e661e7770631a95f0"}];var userStoreRespond = new
> ws.WSRequest();var options = new Array();options.HTTPHeaders =
> headers;options.useSOAP = 1.2;options.useWSA = 1.0;options.action =
> "urn:getSecondaryRealmConfigurations";*
>
> *var payload = '  xmlns:xsd="http://org.apache.axis2/xsd " />';*
> var result;
> try {
>
> *userStoreRespond.open(options,
> "https://10.100.7.102:9443/services/UserStoreConfigAdminService.UserStoreConfigAdminServiceHttpsSoap12Endpoint/
> ",
> false); userStoreRespond.send(payload);*
> result = userStoreRespond.responseE4X;
> } catch (e) {
> log.error(e.toString());
> }


*Error Log:*

>
> [2015-09-28 11:12:39,831] ERROR
> {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
> java.lang.NullPointerException
> at
> org.wso2.carbon.identity.oauth2.validators.DefaultOAuth2TokenValidator.validateScope(DefaultOAuth2TokenValidator.java:52)
> at
> org.wso2.carbon.identity.oauth2.validators.TokenValidationHandler.findOAuthConsumerIfTokenIsValid(TokenValidationHandler.java:245)
> at
> org.wso2.carbon.identity.oauth2.OAuth2TokenValidationService.findOAuthConsumerIfTokenIsValid(OAuth2TokenValidationService.java:65)
> at
> org.wso2.mdm.oauth.extension.OauthAuthenticator.isAuthenticated(OauthAuthenticator.java:74)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:187)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:96)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:66)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(A

Re: [Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Pumudu Ruhunage]

Hi,

Have you tried something like this?

AutomationContext automationContext;
automationContext = new AutomationContext();
String maximumWaitingTime =
automationContext.getInstance().getProperty("maximumWaitingTime");

It's better if you can check how other integration tests were written and
follow the same pattern to refer automation.xml. (without creating new
automationContext and use already initialized objects etc.)

Regards,
Pumudu

On Mon, Sep 28, 2015 at 2:05 PM, Mushthaq Rumy  wrote:

> Hi Rajeenthani,
>
> I think you need to create an object instance of AutomationContext within
> your java class and proceed with it. The below link[1] might be useful for
> you.
>
> [1]
> http://malinthas.blogspot.com/2014/02/how-to-obtain-configuration-details.html
> .
>
>
>
> On Mon, Sep 28, 2015 at 1:44 PM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi all,
>>
>> I am currently working on writing UI integration tests for product UES
>> using selenium.I have to make maximum waiting time for search element by()
>> as default value.As per discussion it can be configured through
>> automation.xml file. I have added 30> maximumWaitingTime> at automation.xml file.So I need to get the value of
>> it for test java classes.Can anyone please give any suggestion on how to
>> get that value?
>>
>> --
>>
>> *Thank You.*
>>
>> *Rajeenthini Satkunam*
>>
>> *Associate Software Engineer | WSO2*
>>
>>
>> *E:rajeenth...@wso2.com *
>>
>> *M :+94770832823 <%2B94770832823>   *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> Thanks & Regards,
> --
> Mushthaq Rumy
> *Software Engineer*
> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Pumudu Ruhunage
Associate Software Engineer | WSO2 Inc
M: +94 779 664493  | http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Mushthaq Rumy]

Hi Rajeenthani,

I think you need to create an object instance of AutomationContext within
your java class and proceed with it. The below link[1] might be useful for
you.

[1]
http://malinthas.blogspot.com/2014/02/how-to-obtain-configuration-details.html
.



On Mon, Sep 28, 2015 at 1:44 PM, Rajeenthini Satkunam 
wrote:

> Hi all,
>
> I am currently working on writing UI integration tests for product UES
> using selenium.I have to make maximum waiting time for search element by()
> as default value.As per discussion it can be configured through
> automation.xml file. I have added 30 maximumWaitingTime> at automation.xml file.So I need to get the value of
> it for test java classes.Can anyone please give any suggestion on how to
> get that value?
>
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823>   *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

Thanks & Regards,
-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Nuwan Wimalasekara]

Hi Rajeenthini,

You can get the value from automation context as bellow

uesAutomationContext.getConfigurationValue("//maximumWaitingTime")

Thanks,
Nuwanw

On Mon, Sep 28, 2015 at 1:44 PM, Rajeenthini Satkunam 
wrote:

> Hi all,
>
> I am currently working on writing UI integration tests for product UES
> using selenium.I have to make maximum waiting time for search element by()
> as default value.As per discussion it can be configured through
> automation.xml file. I have added 30 maximumWaitingTime> at automation.xml file.So I need to get the value of
> it for test java classes.Can anyone please give any suggestion on how to
> get that value?
>
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823>   *
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [Automation] How to get a value from Automation.xml file to test classes

[Rajeenthini Satkunam]

Hi all,

I am currently working on writing UI integration tests for product UES
using selenium.I have to make maximum waiting time for search element by()
as default value.As per discussion it can be configured through
automation.xml file. I have added 30 at automation.xml file.So I need to get the value of it for test java
classes.Can anyone please give any suggestion on how to get that value?

-- 

*Thank You.*

*Rajeenthini Satkunam*

*Associate Software Engineer | WSO2*


*E:rajeenth...@wso2.com *

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

[Dev] UES build failure after updating to identity 4.6.0.alpha

[Udara Rathnayake]

Hi Identity team,

Getting following build failure. Any idea about this?
Do we need to add org.slf4j as a dependency?

Software being installed: OAuth Feature 4.6.0.alpha
(org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
 Missing requirement: oltu 1.0.0.wso2v1 (oltu 1.0.0.wso2v1) requires
'package org.slf4j [1.6.1,1.7.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - OAuth Common 4.6.0.alpha
(org.wso2.carbon.identity.oauth.common 4.6.0.alpha)
  To: package org.apache.oltu.oauth2.common.validators [1.0.0,1.1.0)
 Cannot satisfy dependency:
  From: Identity OAuth Common Feature 4.6.0.alpha
(org.wso2.carbon.identity.oauth.common.feature.group 4.6.0.alpha)
  To: org.wso2.carbon.identity.oauth.common [4.6.0.alpha]
 Cannot satisfy dependency:
  From: OAuth Feature 4.6.0.alpha
(org.wso2.carbon.identity.oauth.feature.group 4.6.0.alpha)
  To: org.wso2.carbon.identity.oauth.common.feature.group [4.6.0.alpha]
Application failed, log file location:
/tmp/m2-ues/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1443427357769.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 User Engagement Server ... SUCCESS [0.831s]
[INFO] UES Server - UI styles  SUCCESS [1.259s]
[INFO] WSO2 Carbon - User Engagement Server Feature Module  SUCCESS [0.038s]
[INFO] WSO2 Carbon - UES feature . SUCCESS [0.570s]
[INFO] UES - Profile Generation .. FAILURE [11.531s]
[INFO] WSO2 User Engagement Server - Distribution  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 15.019s
[INFO] Finished at: Mon Sep 28 13:32:41 IST 2015
[INFO] Final Memory: 23M/329M

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

Re: [Dev] [AF] Error while creating a version for existing application.

[Amalka Subasinghe]

I will try this fix and update soon

On Thu, Sep 24, 2015 at 3:01 PM, Kasun De Silva  wrote:

> Hi Amalka,
>
> According to the registry team this could be possibly fix with the
> following change into the RxtManager. Is this intermittent?  Can you
> reproduce this regularly? This should be reproducible in our local setups
> right? Is so please patch the appfactory.core with the diff provided, and
> test. Let us know the results.
>
> diff --git
> a/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
> b/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
> index 3259299..609419d 100644
> ---
> a/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
> +++
> b/modules/components/org.wso2.carbon.appfactory.core/src/main/java/org/wso2/carbon/appfactory/core/governance/RxtManager.java
> @@ -200,6 +200,7 @@ public class RxtManager {
>  factory.setProperty(XMLInputFactory.IS_COALESCING, true);
>  XMLStreamReader reader = null;
>  reader = factory.createXMLStreamReader(new
> StringReader(info));
> +   GovernanceUtils.loadGovernanceArtifacts(userRegistry);
>  GenericArtifactManager manager = new
> GenericArtifactManager(userRegistry, key);
>  GenericArtifact artifact = manager.newGovernanceArtifact(new
> StAXOMBuilder(reader).getDocumentElement());
>
>
> Thanks,
> Kasun
>
>
> *Kasun de Silva*
> Software Engineer | *WSO2 Inc.*; http://wso2.com
> lean.enterprise.middleware
>
> email   : kas...@wso2.com
> mobile : +94 77 794 4260
>
>
> On Tue, Sep 15, 2015 at 2:08 PM, Amalka Subasinghe 
> wrote:
>
>> Hi,
>>
>>
>> I got the following error, when I try to create a version in an existing
>> application
>>
>> By referring the logs, we can see that config and governance registries
>> are being loaded.
>>
>> TID: [0] [AF] [2015-09-15 01:06:23,476]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at config in 5ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>
>> TID: [0] [AF] [2015-09-15 01:06:23,619]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at governance in 12ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>>
>>
>> however, after I login to the carbon console, using the same tenant I
>> could create the version without errors.
>>
>>
>> TID: [0] [AF] [2015-09-14 21:02:41,818] ERROR
>> {org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl}
>> -  Error in associating lifecycle for the artifact. id:
>> e47109a2-893b-4c7d-a76a-1fc46aa25954, path:
>> /repository/applications/aftestsetupmonitori/1.0.0.
>> {org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl}
>>
>> org.wso2.carbon.registry.core.exceptions.RegistryException: Couldn't find
>> aspectName 'ApplicationLifecycle'
>>
>>at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.associateAspect(EmbeddedRegistry.java:2428)
>>
>>at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.associateAspect(CacheBackedRegistry.java:416)
>>
>>at
>> org.wso2.carbon.registry.core.session.UserRegistry.associateAspectInternal(UserRegistry.java:1904)
>>
>>at
>> org.wso2.carbon.registry.core.session.UserRegistry.access$3800(UserRegistry.java:60)
>>
>>at
>> org.wso2.carbon.registry.core.session.UserRegistry$39.run(UserRegistry.java:1876)
>>
>>at
>> org.wso2.carbon.registry.core.session.UserRegistry$39.run(UserRegistry.java:1873)
>>
>>at java.security.AccessController.doPrivileged(Native Method)
>>
>>at
>> org.wso2.carbon.registry.core.session.UserRegistry.associateAspect(UserRegistry.java:1873)
>>
>>at
>> org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.attachLifecycle(GovernanceArtifactImpl.java:276)
>>at
>> org.wso2.carbon.appfactory.core.governance.RxtManager.addArtifact(RxtManager.java:212)
>>
>>
>> Thanks
>> Amalka
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Amalka Subasinghe
Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev