[Dev] Missing Attributes in Token Introspection Response

2017-08-20 Thread Gayan Gunawardana 
Hi Indunil,

Form token introspection response I can get below attributes.

{"scope":"openid","active":true,"token_type":"Bearer","exp":1503061170,"iat":1503057570,"client_id":"oRbEK6KkycbSLGxt3JHciaitPzoa","username":"admin@carbon.super
"}

But some of optional attributes are not included in introspection response

   sub
  OPTIONAL.  Subject of the token, as defined in JWT [RFC7519
].
  Usually a machine-readable identifier of the resource owner who
  authorized this token.

   aud
  OPTIONAL.  Service-specific string identifier or list of string
  identifiers representing the intended audience for this token, as
  defined in JWT [RFC7519 ].

   iss
  OPTIONAL.  String representing the issuer of this token, as
  defined in JWT [RFC7519 ].

Do we have any limitation to support above attributes ?


[1] https://tools.ietf.org/html/rfc7662

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

Re: [Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

2017-08-20 Thread Asanka Abeyweera 
Hi Abimaran and all,

Is the requirement to expose as SPI service something introduced in Carbon
5? I am curious on how it worked with APIM 2.1.0. Can't we do the same
thing?

On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan 
wrote:

> Hi,
>
> We are embedding Message Broker feature into API Manager 3.0 core, now API
> Manager will function as both MB server and client to manage its artifacts
> such as API, application, subscription, throttling etc between its nodes
> and Gateway. andes-client [1] will function as JMS client for embedded MB.
>
> I'm getting the following exception [3] while starting API Manager. When I
> check the OSGi console for available services with 'ls', I don't see any
> services from andes-client, but andes-client bundle is active. Please find
> the half committed PR [2].
>
> I learned that, on top of wrapping a library as OSGI bundle, we have to
> expose them as SPI services too. So the issue here is, andes-client library
> isn't exposing any SPI service to consume by carbon-jndi.
>
> Carbon team please confirm.
>
> [1]: https://github.com/wso2/andes/blob/v3.2.22/modules/
> orbit/andes-client/pom.xml
> [2]: https://github.com/wso2/carbon-apimgt/pull/4421
> [3]:
> [2017-08-21 09:28:17,041] ERROR {org.wso2.carbon.apimgt.core.util.BrokerUtil}
> - Could not create a JMS client connection from the class 
> javax.naming.NoInitialContextException:
> Cannot find the InitialContextFactory org.wso2.andes.jndi.
> PropertiesFileInitialContextFactory.
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.lambda$
> getInitialContextInternal$28(JNDIContextManagerImpl.java:118)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.
> getInitialContextInternal(JNDIContextManagerImpl.java:118)
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.
> newInitialContext(JNDIContextManagerImpl.java:68)
> at org.wso2.carbon.jndi.internal.osgi.factory.
> DefaultContextFactory.lambda$getInitialContext$21(
> DefaultContextFactory.java:68)
> at org.wso2.carbon.jndi.internal.util.LambdaExceptionUtils.
> lambda$rethrowFunction$2(LambdaExceptionUtils.java:120)
> at java.util.Optional.map(Optional.java:215)
> at org.wso2.carbon.jndi.internal.osgi.factory.DefaultContextFactory.
> getInitialContext(DefaultContextFactory.java:68)
> at javax.naming.spi.NamingManager.getInitialContext(
> NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
> at javax.naming.InitialContext.init(InitialContext.java:244)
> at javax.naming.InitialContext.(InitialContext.java:216)
> at org.wso2.carbon.apimgt.core.impl.BrokerImpl.(BrokerImpl.java:59)
> at org.wso2.carbon.apimgt.core.internal.BundleActivator.
> start(BundleActivator.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:235)
> 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:109)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(
> BundleContextImpl.java:915)
> 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:862)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEvent(ServiceRegistry.java:801)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.
> register(ServiceRegistrationImpl.java:127)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> registerService(ServiceRegistry.java:225)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(
> BundleContextImpl.java:464)
> at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(
> InstanceProcess.java:536)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:213)
> at

Re: [Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

2017-08-20 Thread Abimaran Kugathasan 
+Thusitha, +Jayanga

On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan 
wrote:

> Hi,
>
> We are embedding Message Broker feature into API Manager 3.0 core, now API
> Manager will function as both MB server and client to manage its artifacts
> such as API, application, subscription, throttling etc between its nodes
> and Gateway. andes-client [1] will function as JMS client for embedded MB.
>
> I'm getting the following exception [3] while starting API Manager. When I
> check the OSGi console for available services with 'ls', I don't see any
> services from andes-client, but andes-client bundle is active. Please find
> the half committed PR [2].
>
> I learned that, on top of wrapping a library as OSGI bundle, we have to
> expose them as SPI services too. So the issue here is, andes-client library
> isn't exposing any SPI service to consume by carbon-jndi.
>
> Carbon team please confirm.
>
> [1]: https://github.com/wso2/andes/blob/v3.2.22/modules/
> orbit/andes-client/pom.xml
> [2]: https://github.com/wso2/carbon-apimgt/pull/4421
> [3]:
> [2017-08-21 09:28:17,041] ERROR {org.wso2.carbon.apimgt.core.util.BrokerUtil}
> - Could not create a JMS client connection from the class 
> javax.naming.NoInitialContextException:
> Cannot find the InitialContextFactory org.wso2.andes.jndi.
> PropertiesFileInitialContextFactory.
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.lambda$
> getInitialContextInternal$28(JNDIContextManagerImpl.java:118)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.
> getInitialContextInternal(JNDIContextManagerImpl.java:118)
> at org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.
> newInitialContext(JNDIContextManagerImpl.java:68)
> at org.wso2.carbon.jndi.internal.osgi.factory.
> DefaultContextFactory.lambda$getInitialContext$21(
> DefaultContextFactory.java:68)
> at org.wso2.carbon.jndi.internal.util.LambdaExceptionUtils.
> lambda$rethrowFunction$2(LambdaExceptionUtils.java:120)
> at java.util.Optional.map(Optional.java:215)
> at org.wso2.carbon.jndi.internal.osgi.factory.DefaultContextFactory.
> getInitialContext(DefaultContextFactory.java:68)
> at javax.naming.spi.NamingManager.getInitialContext(
> NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
> at javax.naming.InitialContext.init(InitialContext.java:244)
> at javax.naming.InitialContext.(InitialContext.java:216)
> at org.wso2.carbon.apimgt.core.impl.BrokerImpl.(BrokerImpl.java:59)
> at org.wso2.carbon.apimgt.core.internal.BundleActivator.
> start(BundleActivator.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:235)
> 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:109)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(
> BundleContextImpl.java:915)
> 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:862)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEvent(ServiceRegistry.java:801)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.
> register(ServiceRegistrationImpl.java:127)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> registerService(ServiceRegistry.java:225)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(
> BundleContextImpl.java:464)
> at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(
> InstanceProcess.java:536)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:213)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at

[Dev] Getting exception while using andes-client lib as JMS client for API Manager 3.0.

2017-08-20 Thread Abimaran Kugathasan 
Hi,

We are embedding Message Broker feature into API Manager 3.0 core, now API
Manager will function as both MB server and client to manage its artifacts
such as API, application, subscription, throttling etc between its nodes
and Gateway. andes-client [1] will function as JMS client for embedded MB.

I'm getting the following exception [3] while starting API Manager. When I
check the OSGi console for available services with 'ls', I don't see any
services from andes-client, but andes-client bundle is active. Please find
the half committed PR [2].

I learned that, on top of wrapping a library as OSGI bundle, we have to
expose them as SPI services too. So the issue here is, andes-client library
isn't exposing any SPI service to consume by carbon-jndi.

Carbon team please confirm.

[1]:
https://github.com/wso2/andes/blob/v3.2.22/modules/orbit/andes-client/pom.xml
[2]: https://github.com/wso2/carbon-apimgt/pull/4421
[3]:
[2017-08-21 09:28:17,041] ERROR
{org.wso2.carbon.apimgt.core.util.BrokerUtil} - Could not create a JMS
client connection from the class javax.naming.NoInitialContextException:
Cannot find the InitialContextFactory
org.wso2.andes.jndi.PropertiesFileInitialContextFactory.
at
org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.lambda$getInitialContextInternal$28(JNDIContextManagerImpl.java:118)
at java.util.Optional.orElseThrow(Optional.java:290)
at
org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.getInitialContextInternal(JNDIContextManagerImpl.java:118)
at
org.wso2.carbon.jndi.internal.osgi.JNDIContextManagerImpl.newInitialContext(JNDIContextManagerImpl.java:68)
at
org.wso2.carbon.jndi.internal.osgi.factory.DefaultContextFactory.lambda$getInitialContext$21(DefaultContextFactory.java:68)
at
org.wso2.carbon.jndi.internal.util.LambdaExceptionUtils.lambda$rethrowFunction$2(LambdaExceptionUtils.java:120)
at java.util.Optional.map(Optional.java:215)
at
org.wso2.carbon.jndi.internal.osgi.factory.DefaultContextFactory.getInitialContext(DefaultContextFactory.java:68)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.(InitialContext.java:216)
at org.wso2.carbon.apimgt.core.impl.BrokerImpl.(BrokerImpl.java:59)
at
org.wso2.carbon.apimgt.core.internal.BundleActivator.start(BundleActivator.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
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:109)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
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:862)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
at
org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
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:109)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at

Re: [Dev] [IS] Need to get the consent page back in SSO flow

2017-08-20 Thread Naduni Pamudika 
Hi Isura & Indunil,

On Fri, Aug 18, 2017 at 6:58 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi Naduni,
>
> This was an improvement for IS 5.2.0 (Refer [1] for more information). As
> isura mentioned, you can use "updateApproveAlwaysForAppCons
> entByResourceOwner" in OAuthAdminService to revoke the approve always
> consent for OAuth apps.
>
> Please refer the IDN_OPENID_USER_RPS table in IS. When users login to
> oauth applications, the consent details are stored in this table. In
> there, TRUSTED_ALWAYS column contains the value of "TRUE" or "FALSE" which
> indicates whether the user has given the  “Approve Always” or “Approve”
> options.
>
> We are setting the TRUSTED_ALWAYS column by the value provided for
> "state" when invoking "updateApproveAlwaysForAppConsentByResourceOwner"
> service method. So in order to revoke the "Approve Always" consent, you
> need to provide "state" as "FALSE".
>

Thank you for the detailed responses. I got the issue solved.

Thanks,
Naduni

>
> [1] https://wso2.org/jira/browse/IDENTITY-4832
>
> On Fri, Aug 18, 2017 at 5:34 PM, Naduni Pamudika  wrote:
>
>> Hi Isura,
>>
>> On Fri, Aug 18, 2017 at 4:17 PM, Isura Karunaratne 
>> wrote:
>>
>>> Hi Nipuni,
>>>
>>> You can use updateApproveAlwaysForAppConsentByResourceOwner method in
>>> oauthAdminSevice to revoke the approve always consent.
>>>
>>>  http://schemas.
>> xmlsoap.org/soap/envelope/
>> "
>> xmlns:xsd="http://org.apache.axis2/xsd
>> 
>> ">
>>   
>>   
>>  
>> 
>> ?
>> 
>> ?
>>  
>>   
>> 
>>
>> What do we need to put as "state" here?
>>
>> For the "appName", is it okay to put the Service Provider ID.
>>
>>
>> ​
>> Thanks,
>> Naduni
>>
>> Thanks
>>> Isura
>>>
>>> On Fri, Aug 18, 2017 at 3:24 PM Farasath Ahamed 
>>> wrote:
>>>
 + Indunil

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



 On Fri, Aug 18, 2017 at 3:12 PM, Naduni Pamudika 
 wrote:

> Hi All,
>
> In the SSO flow, first the login page appears and then the consent
> page where the scopes are being approved by the user. I have put
> "Approve Always" for the scopes showing in the consent page and then
> the consent page does not appear in the login flow.
>
> I want to get the normal flow back, i.e. I want to go through the consent
> page and see the scopes.
>
> I tried deleting the application from the IS side and it did not work.
> Even after deleting and creating a new application, "Approve Always" is
> still enabled.
>
> How can I get it disabled?
>
> Thank you,
> Naduni
>
> --
> *Naduni Pamudika*
> Software Engineer | WSO2
> Mobile: +94 719 143658 <+94%2071%20914%203658>
> [image: http://wso2.com/signature] 
>

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

>>> --
>>>
>>> *Isura Dilhara Karunaratne*
>>> Associate Technical Lead | WSO2
>>> Email: is...@wso2.com
>>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>>> Blog : http://isurad.blogspot.com/
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Naduni Pamudika*
>> Software Engineer | WSO2
>> Mobile: +94 719 143658 <+94%2071%20914%203658>
>> [image: http://wso2.com/signature] 
>>
>
>
>
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255
>



-- 
*Naduni Pamudika*
Software Engineer | WSO2
Mobile: +94 719 143658 <+94%2071%20914%203658>
[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Need to get the consent page back in SSO flow

2017-08-20 Thread Naduni Pamudika 
Hi Indunil,

On Fri, Aug 18, 2017 at 7:16 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

>
> Hi,
> On Fri, Aug 18, 2017 at 3:12 PM, Naduni Pamudika  wrote:
>
>> Hi All,
>>
>> In the SSO flow, first the login page appears and then the consent page where
>> the scopes are being approved by the user. I have put "Approve Always" for
>> the scopes showing in the consent page and then the consent page does
>> not appear in the login flow.
>>
>> I want to get the normal flow back, i.e. I want to go through the consent
>> page and see the scopes.
>>
>> I tried deleting the application from the IS side and it did not work.
>> Even after deleting and creating a new application, "Approve Always" is
>> still enabled.
>>
>
> There was an issue when removing an authorized app, the consent was not
> get removed from IDN_OPENID_USER_RPS table and it was fixed with [1]. In
> order to remove the authorized app, you use "Remove Application" in
> "Authorized Apps" gadget [2]? If so, it should remove the consent for that
> application.
>
It worked. Thank you so much for the quick response.

Thanks,
Naduni

>
> [1] https://wso2.org/jira/browse/IDENTITY-4832
> [2] https://docs.wso2.com/display/IS530/Using+the+End+User+Dashboard#
> UsingtheEndUserDashboard-Workingwithyourauthorizedapplications
>
>
>>
>> How can I get it disabled?
>>
>> Thank you,
>> Naduni
>>
>> --
>> *Naduni Pamudika*
>> Software Engineer | WSO2
>> Mobile: +94 719 143658 <+94%2071%20914%203658>
>> [image: http://wso2.com/signature] 
>>
>
>
>
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
> Mobile   0772182255
>



-- 
*Naduni Pamudika*
Software Engineer | WSO2
Mobile: +94 719 143658 <+94%2071%20914%203658>
[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Display the roles of a custom user store for Identity Server

2017-08-20 Thread Isura Karunaratne 
Hi Thomas,

It is wrong to set tenantId as follows for carbon.super tenant. Super
tenant's tenantID is -1234. Can you attach full exception stacktrace.

carbonContext.setTenantId(64302);


Thanks
Isura.

On Fri, Aug 18, 2017 at 6:50 PM, Thomas LEGRAND <
thomas.legr...@versusmind.eu> wrote:

> Hello there,
>
> I found the problem concerning the roles. The Identity Server calls the
> primary user store because the usernames in the list aren't prefixed with
> the domain of the secondary store (which is my custom user store).
> So I modified it and I enter into the method.
>
> Now, I have this weird exception I never encountered before:
>
> [2017-08-18 15:16:04,866] ERROR 
> {org.wso2.carbon.user.core.common.AbstractUserStoreManager}
> -  Error occurred while accessing Java Security Manager Privilege Block
> [2017-08-18 15:16:04,867] ERROR {org.wso2.carbon.user.mgt.UserRealmProxy}
> -  org.wso2.carbon.user.core.UserStoreException: Error occurred while
> accessing Java Security Manager Privilege Block
> [2017-08-18 15:16:04,881] ERROR {org.wso2.carbon.user.mgt.ui.UserAdminClient}
> -  Error occurred while accessing Java Security Manager Privilege Block
>
> Regards,
>
> Thomas
>
> 2017-08-18 14:35 GMT+02:00 Thomas LEGRAND :
>
>> Hello Isura!
>>
>> I did override the methods except the doGetInternalRoleListOfUser because
>> the AbstractUserStoreManager already implements it.
>>
>> Here is my custom store manager in [1] and my "internal" class in [2]. In
>> [3], you will have the user store properties managed by my user store.
>>
>> The goal of the test is to retrieve the roles of a user from the
>> secondary user store implemented by this code by using the interface of the
>> identity server. So you will have a "getRoleListOfUser()" which appears in
>> the logs.
>>
>> [1] CustomUserStoreManager.java
>> [2] CustomUserStoreManagerDSComponent.java
>> [3] CustomUserStoreProperties.java
>>
>> 2017-08-18 12:10 GMT+02:00 Isura Karunaratne :
>>
>>> Hi Thomas,
>>>
>>> Did you override doCheckExistingUser method in your custom user store
>>> manager? In order to view the roles list of the user, following methods
>>> should be overridden.
>>>
>>>
>>>-
>>>
>>>doCheckExistingUser
>>>
>>>-
>>>
>>>doGetExternalRoleListOfUser
>>>
>>>-
>>>
>>>doGetInternalRoleListOfUser
>>>
>>>
>>>
>>> If the issue still occurs after overriding the doCheckExistingUser
>>> method, please attach your sample code. So we can help you faster.
>>>
>>> Thanks
>>> Isura.
>>>
>>> On Fri, Aug 18, 2017 at 3:09 PM, Thomas LEGRAND <
>>> thomas.legr...@versusmind.eu> wrote:
>>>
 Hello again!

 During my tests, I "reinstalled" a new Identity Server v5.3.0 where I
 let the default configuration for the primary user store.
 I configured my custom secondary user store which retrieves data from a
 database. This custom user store is implemented by extending te
 AbstractUserStoreManager class and I generated a OSGi bundle which I
 dropped in the repository/components/dropins directory.

 So I can see my list of users coming from this user store when I
 display it from the identity server. But, when I want to display the roles
 of a suer, I noticed that the primary user store is called (in my case,
 that was the default 
 org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager
 configured in the user-mgt.xml configuration file) to check if the user
 existed and to retrieve its roles.

 Did I miss something in my implementation of the user store to have the
 effect of the primary user store taking the lead to retrieve the roles
 physically located on the secondary user store?

 Regards,

 Thomas

 2017-08-17 11:22 GMT+02:00 Thomas LEGRAND :

> Hello,
>
> I really don't understand why my "external" roles don't appear in the
> list and why no role methods are called in my connector because, when I
> configure a LDAP one, I can see the roles retrieved from the LDAP are
> listed with the internal ones.
>
> I set the log level to DEBUG to see that the LDAP user store is
> calling the internal role retrieval method before checking if the user
> exists:
>
> [2017-08-17 11:18:00,647] DEBUG 
> {org.wso2.carbon.user.core.common.AbstractUserStoreManager}
> -  Retrieving internal roles for user name :  a.bresson and search filter 
> *
> [2017-08-17 11:18:00,648] DEBUG {org.wso2.carbon.user.core.lda
> p.ReadOnlyLDAPUserStoreManager} -  Searching for user a.bresson
>
> But in my case, the user check method isn't even called!
>
> If I continue with the logs, I can see that:
>
> [2017-08-17 11:18:00,653] DEBUG {org.wso2.carbon.user.core.lda
> p.ReadOnlyLDAPUserStoreManager} -  Reading roles with the
> memberOfProperty Property: memberOf
>
> Following this source

Re: [Dev] Improve Default Claim Handler logic

2017-08-20 Thread Hasanthi Purnima Dissanayake 
Hi Farasath,

The logic behind returning claims in 'oidc' is based on the intersection of
both sp requested claims and the registry defined claims for the scope. So
in order to return a specific claims it should define in the registry and
it should define as a requested claims.

2. Improve the fix[2] to return all claims for *openid *flow only when
> service provider has no requested claims.
>
>  So why do we need to return all the claims for openid flow when the SP
has no requested claims?

Thanks,

Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com
M :0718407133| http://wso2.com 

On Mon, Aug 21, 2017 at 9:11 AM, Rushmin Fernando  wrote:

> yes, we should get rid of unwanted processing.
>
> IMO we should honour the configured requested claims in the service
> provider. But I'm not aware whether there was a need to send all the claims
> for open id.
>
>
>
> On Sat, Aug 19, 2017 at 7:48 PM, Farasath Ahamed 
> wrote:
>
>> Hi All,
>>
>> In the current implementation of the DefaultClaimHandler[1] claim
>> handling logic involves the below steps when retrieving claims for local
>> and federated scenarios,
>>
>> 1. Loading local claims and claims mappings
>> 2. Loading all non-empty claims of the user
>>
>> #1 involves several DB calls where as step #2 results in a call to the
>> user store which means either a DB call or LDAP/AD call depending on the
>> user store configured.
>>
>> Here are few shortcoming I noticed,
>>
>>1. If a service provider has configured no requested claims, we
>>simply return an empty map of claims after going through the whole process
>>#1 and #2.
>>2. For authentication involved with flows like OAuth which do not
>>involve claims going through this claims handling logic doesn't make any
>>sense.
>>
>>
>> To give an idea of the performance impact, An authentication request
>> coming into the Authentication Framework takes about 950ms to complete. Of
>> this around 550ms is spent on handling claims (that's close to ~60%). So
>> for an OAuth flow with authorization code or implicit flow, this is a
>> performance hit.
>>
>> I initially did a fix for this[2], by returning an empty map of claims if
>> the there were no requested claims. But this doesn't seem to work since we
>> seem to return all available claims for *openid *flow[3].
>>
>> Do we have a specific reason for return all available claims in the
>> openid flow? Shouldn't we honour service provider requested claims when
>> sending out user claims out of the framework?
>>
>>
>> I have a few improvements in my mind to overcome the problem,
>>
>> 1. Specifically, check for the *oauth *request type and stop executing
>> claim handling logic.
>> 2. Improve the fix[2] to return all claims for *openid *flow only when
>> service provider has no requested claims.
>>
>> Do you see any complexities that could arise with the suggested
>> improvements?
>>
>>
>> [1] https://github.com/wso2/carbon-identity-framework/blob/m
>> aster/components/authentication-framework/org.wso2.carbon.id
>> entity.application.authentication.framework/src/main/java/
>> org/wso2/carbon/identity/application/authentication/
>> framework/handler/claims/impl/DefaultClaimHandler.java
>>
>> [2] https://github.com/wso2/carbon-identity-framework/pull/961
>>
>> [3] https://github.com/wso2/carbon-identity-framework/blob/m
>> aster/components/authentication-framework/org.wso2.carbon.id
>> entity.application.authentication.framework/src/main/java/
>> org/wso2/carbon/identity/application/authentication/
>> framework/handler/claims/impl/DefaultClaimHandler.java#L422
>>
>>
>> Thanks,
>> Farasath Ahamed
>> Software Engineer, WSO2 Inc.; http://wso2.com
>> Mobile: +94777603866
>> Blog: blog.farazath.com
>> Twitter: @farazath619 
>> 
>>
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Improve Default Claim Handler logic

2017-08-20 Thread Rushmin Fernando 
yes, we should get rid of unwanted processing.

IMO we should honour the configured requested claims in the service
provider. But I'm not aware whether there was a need to send all the claims
for open id.



On Sat, Aug 19, 2017 at 7:48 PM, Farasath Ahamed  wrote:

> Hi All,
>
> In the current implementation of the DefaultClaimHandler[1] claim handling
> logic involves the below steps when retrieving claims for local and
> federated scenarios,
>
> 1. Loading local claims and claims mappings
> 2. Loading all non-empty claims of the user
>
> #1 involves several DB calls where as step #2 results in a call to the
> user store which means either a DB call or LDAP/AD call depending on the
> user store configured.
>
> Here are few shortcoming I noticed,
>
>1. If a service provider has configured no requested claims, we simply
>return an empty map of claims after going through the whole process #1 and
>#2.
>2. For authentication involved with flows like OAuth which do not
>involve claims going through this claims handling logic doesn't make any
>sense.
>
>
> To give an idea of the performance impact, An authentication request
> coming into the Authentication Framework takes about 950ms to complete. Of
> this around 550ms is spent on handling claims (that's close to ~60%). So
> for an OAuth flow with authorization code or implicit flow, this is a
> performance hit.
>
> I initially did a fix for this[2], by returning an empty map of claims if
> the there were no requested claims. But this doesn't seem to work since we
> seem to return all available claims for *openid *flow[3].
>
> Do we have a specific reason for return all available claims in the openid
> flow? Shouldn't we honour service provider requested claims when sending
> out user claims out of the framework?
>
>
> I have a few improvements in my mind to overcome the problem,
>
> 1. Specifically, check for the *oauth *request type and stop executing
> claim handling logic.
> 2. Improve the fix[2] to return all claims for *openid *flow only when
> service provider has no requested claims.
>
> Do you see any complexities that could arise with the suggested
> improvements?
>
>
> [1] https://github.com/wso2/carbon-identity-framework/blob/
> master/components/authentication-framework/org.wso2.carbon.
> identity.application.authentication.framework/src/
> main/java/org/wso2/carbon/identity/application/authentication/framework/
> handler/claims/impl/DefaultClaimHandler.java
>
> [2] https://github.com/wso2/carbon-identity-framework/pull/961
>
> [3] https://github.com/wso2/carbon-identity-framework/blob/
> master/components/authentication-framework/org.wso2.carbon.
> identity.application.authentication.framework/src/
> main/java/org/wso2/carbon/identity/application/authentication/framework/
> handler/claims/impl/DefaultClaimHandler.java#L422
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>


-- 
*Best Regards*

*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

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

Re: [Dev] Summarization of JSON data in DAS

2017-08-20 Thread Lahiru Madushanka 
Hi Grainier,

Thanks for the reply. I had a discussion with Nirmal and the final solution
was to use Siddhi Map extension as you also suggesting.
However we change our approach later to push avg data directly from the
device agent, than computing them in DAS. (EDGE analytics)

Anyway thanks for the reply, we can use the suggested approach in future
cases.

Regards,
Lahiru


On Mon, Aug 21, 2017 at 8:20 AM, Grainier Perera  wrote:

> Hi Lahiru,
>
> You can achieve that by using JSON custom mapping [1] + Siddhi MAP
> extension + IfThenElse (optional to check the availability of attributes).
> Basically what you have to do is, have a;
>
> JSON structure like this;
>
>>
>> {
>>"userData": {
>>"timestamp": 19900813115534,
>>
>> *"dataMap": {*
>>
>> *  "id": 1, // these will be your arbitary data
>> "name": grainier**   }*
>>}
>>}
>> }
>
>
> Input mapping like this;
>
>> 
>
>    // other mappings
>
>
>>
>>
>> *
>>   ***
>> 
>
>
> Stream definition like this;
>
>> {
>>   "streamId": "org.wso2.event.user.stream:1.0.0",
>>   "name": "org.wso2.event.user.stream",
>>   "version": "1.0.0",
>>   "nickName": "",
>>   "description": "",
>>   "metaData": [],
>>   "correlationData": [],
>>   "payloadData": [
>> {
>>   "name": "timestamp",
>>   "type": "LONG"
>> },
>>
>>
>>
>> *{  "name": "userData",  "type": "STRING"**}*
>>   ]
>> }
>
>
> Finally within the execution plan;
>
>> @Import('org.wso2.event.user.stream:1.0.0')
>> define stream dataIn (timestamp long, *userData** string*);
>>
>
>
> from dataIn
>> select *map:createFromJSON(**userData) as userData**Map*
>> insert into tempStream;
>
>
>
> from tempStream
>>
>> *select map:get(userDataMap, "id") as id, map:get(userDataMap, "name") as
>> name*insert into tempStream2;
>
>
>
> -- now you can use those arbitary fields here...
>
>
>
> Hope that helped...
>
> [1] https://docs.wso2.com/display/CEP420/Input+Mapping+
> Types#InputMappingTypes-JSONinputmappingJSONInputMapping
> [2] https://docs.wso2.com/display/CEP420/Map+Extension
>
> Regards,
> Grainier.
>
> On Sat, Jul 8, 2017 at 11:34 AM, Lahiru Madushanka 
> wrote:
>
>> Hi Nirmal,
>>
>> Documentation says arbitrary data support can be used with wso2event
>> input format. But in my case its "JSON".
>> Custom event receiver will be an option. But is there a way I can do this
>> without writing a custom event receiver ?
>>
>> Thanks for the help.
>>
>> Regards,
>> Lahiru
>>
>> On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando  wrote:
>>
>>> Check on arbitrary data support https://docs.wso2.com/
>>> display/DAS310/Input+Mapping+Types
>>>
>>> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka 
>>> wrote:
>>>
 Hi all,

 I have a requirement where data values published to DAS are not
 predefined (dynamic)
 ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
 Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores":
 4}
 This JSON string will be changed with no of cores in the PC which
 pushes the data.

 Is there a way I can write a summarization query in siddhiql to take
 average of average corePercentages for a time interval. (first take avg of
 percentage values and then average it over time )

 Thanks
 Lahiru

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


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Technical Lead, WSO2 Inc.
>>> Mobile: +94715779733 <+94%2071%20577%209733>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Grainier Perera
> Senior Software Engineer
> Mobile : +94716122384 <+94%2071%20612%202384>
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Summarization of JSON data in DAS

2017-08-20 Thread Grainier Perera 
Hi Lahiru,

You can achieve that by using JSON custom mapping [1] + Siddhi MAP
extension + IfThenElse (optional to check the availability of attributes).
Basically what you have to do is, have a;

JSON structure like this;

>
> {
>"userData": {
>"timestamp": 19900813115534,
>
> *"dataMap": {*
>
> *  "id": 1, // these will be your arbitary data
> "name": grainier**   }*
>}
>}
> }


Input mapping like this;

> 

   // other mappings


>
>
> *
>   ***
> 


Stream definition like this;

> {
>   "streamId": "org.wso2.event.user.stream:1.0.0",
>   "name": "org.wso2.event.user.stream",
>   "version": "1.0.0",
>   "nickName": "",
>   "description": "",
>   "metaData": [],
>   "correlationData": [],
>   "payloadData": [
> {
>   "name": "timestamp",
>   "type": "LONG"
> },
>
>
>
> *{  "name": "userData",  "type": "STRING"**}*
>   ]
> }


Finally within the execution plan;

> @Import('org.wso2.event.user.stream:1.0.0')
> define stream dataIn (timestamp long, *userData** string*);
>


from dataIn
> select *map:createFromJSON(**userData) as userData**Map*
> insert into tempStream;



from tempStream
>
> *select map:get(userDataMap, "id") as id, map:get(userDataMap, "name") as
> name*insert into tempStream2;



-- now you can use those arbitary fields here...



Hope that helped...

[1]
https://docs.wso2.com/display/CEP420/Input+Mapping+Types#InputMappingTypes-JSONinputmappingJSONInputMapping
[2] https://docs.wso2.com/display/CEP420/Map+Extension

Regards,
Grainier.

On Sat, Jul 8, 2017 at 11:34 AM, Lahiru Madushanka 
wrote:

> Hi Nirmal,
>
> Documentation says arbitrary data support can be used with wso2event input
> format. But in my case its "JSON".
> Custom event receiver will be an option. But is there a way I can do this
> without writing a custom event receiver ?
>
> Thanks for the help.
>
> Regards,
> Lahiru
>
> On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando  wrote:
>
>> Check on arbitrary data support https://docs.wso2.com/
>> display/DAS310/Input+Mapping+Types
>>
>> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have a requirement where data values published to DAS are not
>>> predefined (dynamic)
>>> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
>>> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores":
>>> 4}
>>> This JSON string will be changed with no of cores in the PC which pushes
>>> the data.
>>>
>>> Is there a way I can write a summarization query in siddhiql to take
>>> average of average corePercentages for a time interval. (first take avg of
>>> percentage values and then average it over time )
>>>
>>> Thanks
>>> Lahiru
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Technical Lead, WSO2 Inc.
>> Mobile: +94715779733 <+94%2071%20577%209733>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Grainier Perera
Senior Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Where is the create publishers, streams and receivers page in wso2das-4.0.0-M6

2017-08-20 Thread Grainier Perera 
Hi Sagar,

>From SP 4.0.0-MX [1] (formerly DASw-4.0.0-MX) <, we don't have a management
console page (localhost:9443/carbon). Instead, we have the editor. Also,
there are some changes to key concepts such as receivers and publishers.
Instead of receivers and publishers, we have a new concept called event
source[2] and event sink[3], which can be defined within the Siddhi App
(execution plan) it self. Therefore, you don't have to create streams,
receivers, and publishers separately as you did in DAS 3.1.0.

Note: You can find the latest milestone release at [4] with further
improvements.

[1] https://docs.wso2.com/display/SP400/
[2] https://docs.wso2.com/display/SP400/Receiving+Events
[3] https://docs.wso2.com/display/SP400/Publishing+Events
[4] https://github.com/wso2/product-sp/releases/download/
v4.0.0-M9/wso2sp-4.0.0-M9.zip

Regards,
Grainier.

On Sat, Jul 22, 2017 at 11:04 AM, Sagar Kapadia  wrote:

> Hi,
> I installed wso2das-4.0.0-M6, and ran it using the "editor.bat" command.
> However, I cant figure out where is the localhost:9443/carbon page which
> was present in wso2das-3.1.0. I need that to create
> streams, publishers and receivers. The composer in wso2das-4.0.0-M6 allows
> me to handle events by linking streams. But where do I create the steams,
> receivers and publishers themselves?
> Sagar
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Grainier Perera
Senior Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC-2017] [IS] [OAuth DCRM] Integration Test for the implementation of OAuth 2.0 DCRM protocol

2017-08-20 Thread Abilashini Thiyagarajah 
Hi all,

Thanks for the feedback. I have fixed the issues mentioned in the review
comments and also made some modifications.

Please review.

Regards,
Abilashini

*Thiyagarajah Abilashini*
Student
Department of Computer Science and Engineering
University of Moratuwa, Sri Lanka

On 11 August 2017 at 00:12, Dimuthu De Lanerolle  wrote:

> Hi Abilashini,
>
> I have added a few review comments for PR's. Please have a look and fix.
>
> Regards
> DimuthuD
>
> On Thu, Aug 10, 2017 at 8:07 PM, Ishara Karunarathna 
> wrote:
>
>> Hi,
>>
>> Thanks Abilashini, will review the PR
>>
>> -Ishara
>>
>> On Wed, Aug 9, 2017 at 1:05 PM, Abilashini Thiyagarajah <
>> abilashini...@cse.mrt.ac.lk> wrote:
>>
>>> Hi,
>>>
>>> Please find the PR of the integration test cases [1] for the
>>> implementation of OAuth DCRM protocol [2].
>>>
>>> Covered test cases in this PR as follow,
>>>
>>>1. Successful Read service provider
>>>2. Read request with invalid client ID in the endpoint URL
>>>3. Successful update service provider
>>>4. Update request with invalid client ID in the endpoint URL
>>>5. Update request with invalid client ID
>>>6. Update request with invalid client secret
>>>7. Update request without grant type
>>>8. Update request with invalid grant type
>>>9. Successful Delete service provider
>>>10. Delete request with invalid client ID in the endpoint URL
>>>
>>> Please share your feedback to improve further
>>>
>>> [1] https://github.com/wso2/product-is/pull/1293
>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/pull/396
>>>
>>> Best Regards,
>>> Abilashini
>>>
>>> *Thiyagarajah Abilashini*
>>> Student
>>> Department of Computer Science and Engineering
>>> University of Moratuwa, Sri Lanka
>>>
>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <071%20799%206791>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dimuthu De Lanerolle
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middlewear.
> http://wso2.com/
> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invitation: [GSoC][APIM] Environment Support for API Manager weekly ... @ Fri Aug 18, 2017 2:30pm - 3:30pm (Ravindu Perera)

2017-08-20 Thread Ravindu Perera 
Hi
Meeting Notes .


   - Discussed on how to fix the issue CROS and tried some of the suggested
   once.
   - Planned what should be done within the next week.
   - discussed on putting an PR on Monday.

Thank you
Ravindu Perera

On Fri, Aug 18, 2017 at 2:08 PM, Kasun Thennakoon  wrote:

> more details »
> 
> [GSoC][APIM] Environment Support for API Manager weekly sync up meeting
>
> *When*
> Fri Aug 18, 2017 2:30pm – 3:30pm Colombo
>
> *Where*
> WSO2, 20, Palm Grove, Colombo, Sri Lanka (map
> 
> )
>
> *Joining info*
> meet.google.com/ifj-uasw-oij
>
> *Calendar*
> Ravindu Perera
>
> *Who*
> •
> Kasun Thennakoon - organizer
> •
> Thilini Shanika
> •
> Ravindu Perera
> •
> Chanaka Jayasena
> •
> Pubudu Gunatilaka
> •
> dev@wso2.org
> •
> Nuwan Dias
>
> Going?   *Yes
> 
> - Maybe
> 
> - No
> *
> more options »
> 
>
> Invitation from Google Calendar 
>
> You are receiving this email at the account ravindu.2014...@iit.ac.lk
> because you are subscribed for invitations on calendar Ravindu Perera.
>
> To stop receiving these emails, please log in to https://www.google.com/
> calendar/ and change your notification settings for this calendar.
>
> Forwarding this invitation could allow any recipient to modify your RSVP
> response. Learn More
> .
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev