Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga / Ishara,

I'll look in to using client credentials grant for Registration Management
and will start a thread in the architecture list.

I looked in to the implementation of OIDC DCR and found that
registrationAccessToken and registrationClientURI are already added to the
OIDCRegistrationResponseProfile[1] although they are not added to response.

Should we make use of this or make the necessary changes to OAuth DCR
component itself.

[1]
https://github.com/dinuish94/identity-inbound-auth-oauth/blob/v5.3.4/components/org.wso2.carbon.identity.oidc.dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/model/OIDCRegistrationResponseProfile.java

Thanks,
Dinuksha.

On Fri, Apr 14, 2017 at 1:42 PM, Maduranga Siriwardena 
wrote:

>
>
> On Fri, Apr 14, 2017 at 1:21 PM, Ishara Karunarathna 
> wrote:
>
>> Hi Dinuksha,
>>
>> On Fri, Apr 14, 2017 at 9:52 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have already started working on the cloned repo of [1] in order to
>>> make the necessary changes to the DCR component. I need a few
>>> clarifications on below.
>>>
>>> 1) I used Apache Oltu's OAuthIssuer to generate the access token
>>> required for Client Registration Management. Is this fine? Is there any
>>> better way? And also what's the approach to keep these tokens stored on the
>>> server end.
>>>
>> I think you generate your own access token for this, Instead I prefer to
>> use existing client credential grant type (If use is unknown and password
>> grant type if use is known) And use special scope for this.
>>
>> And better to discuss this in architecture list [1] then you can propose
>> your design and get more input.
>> [1]
>>
>
> I think you should use client credentials grant type for this and better
> to discuss this in a mailing thread.
>
>>
>> Thanks,
>> Ishara
>>
>>>
>>> 2) In order to add the two additional fields, registration_access_token
>>> and registration_client_uri, should we modify the existing profiles,
>>> responses etc, or should we extend them and make the necessary changes.
>>>
>> You have to modify the existing profiles and responses if needed. I think
> you only need to modify the response. The reason is there is no scenario
> where the new response is sent and another scenario where the old response
> is sent. In all the situations DCR should send the response with token.
> However check the usages of this response object in OIDC DCR and see if
> there is any conflict.
>
> Thanks,
> Maduranga.
>
>>
>>> I have added the above fields to the existing response and it can be
>>> found at [2]. Kindly provide feedback.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>>> [2] https://github.com/dinuish94/identity-inbound-auth-oauth
>>>
>>> Thanks,
>>> Dinuksha
>>>
>>> On Fri, Apr 14, 2017 at 8:02 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 Glad to hear the progress of the project. Will go through the code and
 let you know if anything need to improve.

 However you might consider working in a fork of the oauth repo [1]
 since you need to do some modifications to dcr component also (to send the
 token with the registration response).

 [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth

 Thanks,

 On Thu, Apr 13, 2017 at 8:05 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
> The repo of the sample implementation is moved to [1]. So far, it
> contains the implementation of the Client Configuration Endpoint where the
> client can query registration data.
>
> The Client Registration info can be obtained by sending a GET request
> to the endpoint /identity/register/{client_id} as below.
>
> curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
> https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua'
> -k -v
> [1] https://github.com/dinuish94/dynamic-client-registration
> -management-component
>
> Thanks,
> Dinuksha
>
> On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi All,
>>
>> I have started implementing a sample component in order to get a
>> better understanding about the code and to gain hands-on experience. So 
>> far
>> I was able to set up the component and register a processor for DCRM
>> similar to what is done in [1] and [2]. The current implementation can be
>> found at [3]. It contains the implementation up to where the request
>> processing is started by DCRMProcessor. I will proceed with the request
>> handing next.
>>
>> Meanwhile, it would be great if you could review the implementation
>> and provide feedback whether the processor registration for identity
>> endpoint is done correctly.
>>

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

On Fri, Apr 14, 2017 at 1:21 PM, Ishara Karunarathna 
wrote:

> Hi Dinuksha,
>
> On Fri, Apr 14, 2017 at 9:52 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I have already started working on the cloned repo of [1] in order to make
>> the necessary changes to the DCR component. I need a few clarifications on
>> below.
>>
>> 1) I used Apache Oltu's OAuthIssuer to generate the access token required
>> for Client Registration Management. Is this fine? Is there any better way?
>> And also what's the approach to keep these tokens stored on the server end.
>>
> I think you generate your own access token for this, Instead I prefer to
> use existing client credential grant type (If use is unknown and password
> grant type if use is known) And use special scope for this.
>
> And better to discuss this in architecture list [1] then you can propose
> your design and get more input.
> [1]
>

I think you should use client credentials grant type for this and better to
discuss this in a mailing thread.

>
> Thanks,
> Ishara
>
>>
>> 2) In order to add the two additional fields, registration_access_token
>> and registration_client_uri, should we modify the existing profiles,
>> responses etc, or should we extend them and make the necessary changes.
>>
> You have to modify the existing profiles and responses if needed. I think
you only need to modify the response. The reason is there is no scenario
where the new response is sent and another scenario where the old response
is sent. In all the situations DCR should send the response with token.
However check the usages of this response object in OIDC DCR and see if
there is any conflict.

Thanks,
Maduranga.

>
>> I have added the above fields to the existing response and it can be
>> found at [2]. Kindly provide feedback.
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>> [2] https://github.com/dinuish94/identity-inbound-auth-oauth
>>
>> Thanks,
>> Dinuksha
>>
>> On Fri, Apr 14, 2017 at 8:02 AM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> Glad to hear the progress of the project. Will go through the code and
>>> let you know if anything need to improve.
>>>
>>> However you might consider working in a fork of the oauth repo [1] since
>>> you need to do some modifications to dcr component also (to send the token
>>> with the registration response).
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>>>
>>> Thanks,
>>>
>>> On Thu, Apr 13, 2017 at 8:05 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi All,

 The repo of the sample implementation is moved to [1]. So far, it
 contains the implementation of the Client Configuration Endpoint where the
 client can query registration data.

 The Client Registration info can be obtained by sending a GET request
 to the endpoint /identity/register/{client_id} as below.

 curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
 https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua'
 -k -v
 [1] https://github.com/dinuish94/dynamic-client-registration
 -management-component

 Thanks,
 Dinuksha

 On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
> I have started implementing a sample component in order to get a
> better understanding about the code and to gain hands-on experience. So 
> far
> I was able to set up the component and register a processor for DCRM
> similar to what is done in [1] and [2]. The current implementation can be
> found at [3]. It contains the implementation up to where the request
> processing is started by DCRMProcessor. I will proceed with the request
> handing next.
>
> Meanwhile, it would be great if you could review the implementation
> and provide feedback whether the processor registration for identity
> endpoint is done correctly.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
> [2] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
> r/OIDCDCRProcessor.java
> [3] https://github.com/dinuish94/identity-inbound-auth-oauth/
>
> Thanks and regards,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I submitted the final proposal. Would like to thank you for your
>> guidance, support and insight.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Mon, Apr 3, 2017 at 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Ishara Karunarathna]

Hi Dinuksha,

On Fri, Apr 14, 2017 at 9:52 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have already started working on the cloned repo of [1] in order to make
> the necessary changes to the DCR component. I need a few clarifications on
> below.
>
> 1) I used Apache Oltu's OAuthIssuer to generate the access token required
> for Client Registration Management. Is this fine? Is there any better way?
> And also what's the approach to keep these tokens stored on the server end.
>
I think you generate your own access token for this, Instead I prefer to
use existing client credential grant type (If use is unknown and password
grant type if use is known) And use special scope for this.

And better to discuss this in architecture list [1] then you can propose
your design and get more input.
[1]

Thanks,
Ishara

>
> 2) In order to add the two additional fields, registration_access_token
> and registration_client_uri, should we modify the existing profiles,
> responses etc, or should we extend them and make the necessary changes.
>
> I have added the above fields to the existing response and it can be found
> at [2]. Kindly provide feedback.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
> [2] https://github.com/dinuish94/identity-inbound-auth-oauth
>
> Thanks,
> Dinuksha
>
> On Fri, Apr 14, 2017 at 8:02 AM, Maduranga Siriwardena  > wrote:
>
>> Hi Dinuksha,
>>
>> Glad to hear the progress of the project. Will go through the code and
>> let you know if anything need to improve.
>>
>> However you might consider working in a fork of the oauth repo [1] since
>> you need to do some modifications to dcr component also (to send the token
>> with the registration response).
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>>
>> Thanks,
>>
>> On Thu, Apr 13, 2017 at 8:05 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> The repo of the sample implementation is moved to [1]. So far, it
>>> contains the implementation of the Client Configuration Endpoint where the
>>> client can query registration data.
>>>
>>> The Client Registration info can be obtained by sending a GET request to
>>> the endpoint /identity/register/{client_id} as below.
>>>
>>> curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
>>> https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua'
>>> -k -v
>>> [1] https://github.com/dinuish94/dynamic-client-registration
>>> -management-component
>>>
>>> Thanks,
>>> Dinuksha
>>>
>>> On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi All,

 I have started implementing a sample component in order to get a better
 understanding about the code and to gain hands-on experience. So far I was
 able to set up the component and register a processor for DCRM similar to
 what is done in [1] and [2]. The current implementation can be found at
 [3]. It contains the implementation up to where the request processing is
 started by DCRMProcessor. I will proceed with the request handing next.

 Meanwhile, it would be great if you could review the implementation and
 provide feedback whether the processor registration for identity endpoint
 is done correctly.

 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java
 [2] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
 dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
 r/OIDCDCRProcessor.java
 [3] https://github.com/dinuish94/identity-inbound-auth-oauth/

 Thanks and regards,
 Dinuksha.

 On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I submitted the final proposal. Would like to thank you for your
> guidance, support and insight.
>
> Thanks,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinukshi,
>>
>> I will not have time to go through your proposal now. As the deadline
>> is getting closer, please go ahead and submit the proposal.
>>
>> Thanks,
>>
>> On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have made the suggested changes in the proposal. Would appreciate
>>> if you could review and provide feedback.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinushika,

 I have added some 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

I have already started working on the cloned repo of [1] in order to make
the necessary changes to the DCR component. I need a few clarifications on
below.

1) I used Apache Oltu's OAuthIssuer to generate the access token required
for Client Registration Management. Is this fine? Is there any better way?
And also what's the approach to keep these tokens stored on the server end.

2) In order to add the two additional fields, registration_access_token
and registration_client_uri, should we modify the existing profiles,
responses etc, or should we extend them and make the necessary changes.

I have added the above fields to the existing response and it can be found
at [2]. Kindly provide feedback.

[1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
[2] https://github.com/dinuish94/identity-inbound-auth-oauth

Thanks,
Dinuksha

On Fri, Apr 14, 2017 at 8:02 AM, Maduranga Siriwardena 
wrote:

> Hi Dinuksha,
>
> Glad to hear the progress of the project. Will go through the code and let
> you know if anything need to improve.
>
> However you might consider working in a fork of the oauth repo [1] since
> you need to do some modifications to dcr component also (to send the token
> with the registration response).
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>
> Thanks,
>
> On Thu, Apr 13, 2017 at 8:05 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi All,
>>
>> The repo of the sample implementation is moved to [1]. So far, it
>> contains the implementation of the Client Configuration Endpoint where the
>> client can query registration data.
>>
>> The Client Registration info can be obtained by sending a GET request to
>> the endpoint /identity/register/{client_id} as below.
>>
>> curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
>> https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua'
>> -k -v
>> [1] https://github.com/dinuish94/dynamic-client-registration
>> -management-component
>>
>> Thanks,
>> Dinuksha
>>
>> On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I have started implementing a sample component in order to get a better
>>> understanding about the code and to gain hands-on experience. So far I was
>>> able to set up the component and register a processor for DCRM similar to
>>> what is done in [1] and [2]. The current implementation can be found at
>>> [3]. It contains the implementation up to where the request processing is
>>> started by DCRMProcessor. I will proceed with the request handing next.
>>>
>>> Meanwhile, it would be great if you could review the implementation and
>>> provide feedback whether the processor registration for identity endpoint
>>> is done correctly.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>>> sor/DCRProcessor.java
>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>>> r/OIDCDCRProcessor.java
>>> [3] https://github.com/dinuish94/identity-inbound-auth-oauth/
>>>
>>> Thanks and regards,
>>> Dinuksha.
>>>
>>> On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 I submitted the final proposal. Would like to thank you for your
 guidance, support and insight.

 Thanks,
 Dinuksha.

 On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinukshi,
>
> I will not have time to go through your proposal now. As the deadline
> is getting closer, please go ahead and submit the proposal.
>
> Thanks,
>
> On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I have made the suggested changes in the proposal. Would appreciate
>> if you could review and provide feedback.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinushika,
>>>
>>> I have added some comments to the the draft proposal.
>>>
>>> Thanks,
>>>
>>> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi,

 Sorry for the late reply as I had my Semester exams this week. I
 have shared the draft proposal on the GSoC dashboard. Would appreciate 
 if
 you could review and provide feedback.

 Thanks,
 Dinuksha.

 On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinuksha,

Glad to hear the progress of the project. Will go through the code and let
you know if anything need to improve.

However you might consider working in a fork of the oauth repo [1] since
you need to do some modifications to dcr component also (to send the token
with the registration response).

[1] https://github.com/wso2-extensions/identity-inbound-auth-oauth

Thanks,

On Thu, Apr 13, 2017 at 8:05 PM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
> The repo of the sample implementation is moved to [1]. So far, it contains
> the implementation of the Client Configuration Endpoint where the client
> can query registration data.
>
> The Client Registration info can be obtained by sending a GET request to
> the endpoint /identity/register/{client_id} as below.
>
> curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
> https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua' -k
> -v
> [1] https://github.com/dinuish94/dynamic-client-registration-management-
> component
>
> Thanks,
> Dinuksha
>
> On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi All,
>>
>> I have started implementing a sample component in order to get a better
>> understanding about the code and to gain hands-on experience. So far I was
>> able to set up the component and register a processor for DCRM similar to
>> what is done in [1] and [2]. The current implementation can be found at
>> [3]. It contains the implementation up to where the request processing is
>> started by DCRMProcessor. I will proceed with the request handing next.
>>
>> Meanwhile, it would be great if you could review the implementation and
>> provide feedback whether the processor registration for identity endpoint
>> is done correctly.
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/
>> processor/DCRProcessor.java
>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>> r/OIDCDCRProcessor.java
>> [3] https://github.com/dinuish94/identity-inbound-auth-oauth/
>>
>> Thanks and regards,
>> Dinuksha.
>>
>> On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I submitted the final proposal. Would like to thank you for your
>>> guidance, support and insight.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinukshi,

 I will not have time to go through your proposal now. As the deadline
 is getting closer, please go ahead and submit the proposal.

 Thanks,

 On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have made the suggested changes in the proposal. Would appreciate if
> you could review and provide feedback.
>
> Thanks,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinushika,
>>
>> I have added some comments to the the draft proposal.
>>
>> Thanks,
>>
>> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Sorry for the late reply as I had my Semester exams this week. I
>>> have shared the draft proposal on the GSoC dashboard. Would appreciate 
>>> if
>>> you could review and provide feedback.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 Thank you for the information. I shall look in to this and proceed
 with the basic implementation and preparing the proposal. Will keep you
 informed.

 On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinuksha,
>
> DCR has 3 specs.
>
>- OAuth 2.0 Dynamic Client Registration
>- OAuth 2.0 Dynamic Client Registration Management
>- OpenID Connect Dynamic Client Registration
>
> OAuth 2.0 Dynamic Client Registration is handled by [1]. And
> OpenID Connect Dynamic Client Registration is handled by [2]. This is 
> the
> class that handles requests for /identity/connect/register. OAuth
> 2.0 Dynamic Client Registration Management is the one you are going to
> implement.
>
> As a start you can just register a servlet and implement the
> functionality. We will guide you how to register a processor for 
> identity

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi All,

The repo of the sample implementation is moved to [1]. So far, it contains
the implementation of the Client Configuration Endpoint where the client
can query registration data.

The Client Registration info can be obtained by sending a GET request to
the endpoint /identity/register/{client_id} as below.

curl -H 'Authorization: Basic: YWRtaW46YWRtaW4=' -X GET '
https://localhost:9443/identity/register/8VF3iYpzF9LkxDff4MEmwRKxt7Ua' -k -v
[1]
https://github.com/dinuish94/dynamic-client-registration-management-component

Thanks,
Dinuksha

On Thu, Apr 13, 2017 at 11:54 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
> I have started implementing a sample component in order to get a better
> understanding about the code and to gain hands-on experience. So far I was
> able to set up the component and register a processor for DCRM similar to
> what is done in [1] and [2]. The current implementation can be found at
> [3]. It contains the implementation up to where the request processing is
> started by DCRMProcessor. I will proceed with the request handing next.
>
> Meanwhile, it would be great if you could review the implementation and
> provide feedback whether the processor registration for identity endpoint
> is done correctly.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.
> oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/
> dcr/processor/DCRProcessor.java
> [2] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/
> processor/OIDCDCRProcessor.java
> [3] https://github.com/dinuish94/identity-inbound-auth-oauth/
>
> Thanks and regards,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I submitted the final proposal. Would like to thank you for your
>> guidance, support and insight.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena > > wrote:
>>
>>> Hi Dinukshi,
>>>
>>> I will not have time to go through your proposal now. As the deadline is
>>> getting closer, please go ahead and submit the proposal.
>>>
>>> Thanks,
>>>
>>> On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 I have made the suggested changes in the proposal. Would appreciate if
 you could review and provide feedback.

 Thanks,
 Dinuksha.

 On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinushika,
>
> I have added some comments to the the draft proposal.
>
> Thanks,
>
> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi,
>>
>> Sorry for the late reply as I had my Semester exams this week. I have
>> shared the draft proposal on the GSoC dashboard. Would appreciate if you
>> could review and provide feedback.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> Thank you for the information. I shall look in to this and proceed
>>> with the basic implementation and preparing the proposal. Will keep you
>>> informed.
>>>
>>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 DCR has 3 specs.

- OAuth 2.0 Dynamic Client Registration
- OAuth 2.0 Dynamic Client Registration Management
- OpenID Connect Dynamic Client Registration

 OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
 Connect Dynamic Client Registration is handled by [2]. This is the 
 class
 that handles requests for /identity/connect/register. OAuth 2.0
 Dynamic Client Registration Management is the one you are going to
 implement.

 As a start you can just register a servlet and implement the
 functionality. We will guide you how to register a processor for 
 identity
 endpoint, if we decide to go in that path.

 I hope that I answered your questions. Get back to us of you need
 anything clarified.


 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java
 [2] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
 dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi All,

I have started implementing a sample component in order to get a better
understanding about the code and to gain hands-on experience. So far I was
able to set up the component and register a processor for DCRM similar to
what is done in [1] and [2]. The current implementation can be found at
[3]. It contains the implementation up to where the request processing is
started by DCRMProcessor. I will proceed with the request handing next.

Meanwhile, it would be great if you could review the implementation and
provide feedback whether the processor registration for identity endpoint
is done correctly.

[1] https://github.com/wso2-extensions/identity-inbound-
auth-oauth/blob/master/components/org.wso2.carbon.
identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/
oauth/dcr/processor/DCRProcessor.java
[2] https://github.com/wso2-extensions/identity-inbound-
auth-oauth/blob/master/components/org.wso2.carbon.
identity.oidc.dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processor/
OIDCDCRProcessor.java
[3] https://github.com/dinuish94/identity-inbound-auth-oauth/

Thanks and regards,
Dinuksha.

On Mon, Apr 3, 2017 at 8:43 PM, Dinuksha Ishwari  wrote:

> Hi Maduranga,
>
> I submitted the final proposal. Would like to thank you for your guidance,
> support and insight.
>
> Thanks,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena 
> wrote:
>
>> Hi Dinukshi,
>>
>> I will not have time to go through your proposal now. As the deadline is
>> getting closer, please go ahead and submit the proposal.
>>
>> Thanks,
>>
>> On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have made the suggested changes in the proposal. Would appreciate if
>>> you could review and provide feedback.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinushika,

 I have added some comments to the the draft proposal.

 Thanks,

 On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi,
>
> Sorry for the late reply as I had my Semester exams this week. I have
> shared the draft proposal on the GSoC dashboard. Would appreciate if you
> could review and provide feedback.
>
> Thanks,
> Dinuksha.
>
> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> Thank you for the information. I shall look in to this and proceed
>> with the basic implementation and preparing the proposal. Will keep you
>> informed.
>>
>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> DCR has 3 specs.
>>>
>>>- OAuth 2.0 Dynamic Client Registration
>>>- OAuth 2.0 Dynamic Client Registration Management
>>>- OpenID Connect Dynamic Client Registration
>>>
>>> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
>>> Connect Dynamic Client Registration is handled by [2]. This is the class
>>> that handles requests for /identity/connect/register. OAuth 2.0
>>> Dynamic Client Registration Management is the one you are going to
>>> implement.
>>>
>>> As a start you can just register a servlet and implement the
>>> functionality. We will guide you how to register a processor for 
>>> identity
>>> endpoint, if we decide to go in that path.
>>>
>>> I hope that I answered your questions. Get back to us of you need
>>> anything clarified.
>>>
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>>> sor/DCRProcessor.java
>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>>> r/OIDCDCRProcessor.java
>>>
>>> Thanks,
>>>
>>>
>>> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 I have referred the given code [1] and observed that DCRProcessor
 will only process requests that call the endpoint /identity/register as
 OAuth2.0 specification and will not process the the calls to
 /identity/connect/register which is the endpoint specified in 
 OpenIDConnect
 specification for DCR. Correct me if I am wrong.

 I would appreciate if you could provide me some more information
 regarding exposing an endpoint for the custom component of DCRM.

 [1] 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

I submitted the final proposal. Would like to thank you for your guidance,
support and insight.

Thanks,
Dinuksha.

On Mon, Apr 3, 2017 at 7:54 PM, Maduranga Siriwardena 
wrote:

> Hi Dinukshi,
>
> I will not have time to go through your proposal now. As the deadline is
> getting closer, please go ahead and submit the proposal.
>
> Thanks,
>
> On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I have made the suggested changes in the proposal. Would appreciate if
>> you could review and provide feedback.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena > > wrote:
>>
>>> Hi Dinushika,
>>>
>>> I have added some comments to the the draft proposal.
>>>
>>> Thanks,
>>>
>>> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi,

 Sorry for the late reply as I had my Semester exams this week. I have
 shared the draft proposal on the GSoC dashboard. Would appreciate if you
 could review and provide feedback.

 Thanks,
 Dinuksha.

 On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> Thank you for the information. I shall look in to this and proceed
> with the basic implementation and preparing the proposal. Will keep you
> informed.
>
> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinuksha,
>>
>> DCR has 3 specs.
>>
>>- OAuth 2.0 Dynamic Client Registration
>>- OAuth 2.0 Dynamic Client Registration Management
>>- OpenID Connect Dynamic Client Registration
>>
>> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
>> Connect Dynamic Client Registration is handled by [2]. This is the class
>> that handles requests for /identity/connect/register. OAuth 2.0
>> Dynamic Client Registration Management is the one you are going to
>> implement.
>>
>> As a start you can just register a servlet and implement the
>> functionality. We will guide you how to register a processor for identity
>> endpoint, if we decide to go in that path.
>>
>> I hope that I answered your questions. Get back to us of you need
>> anything clarified.
>>
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>> sor/DCRProcessor.java
>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>> r/OIDCDCRProcessor.java
>>
>> Thanks,
>>
>>
>> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have referred the given code [1] and observed that DCRProcessor
>>> will only process requests that call the endpoint /identity/register as
>>> OAuth2.0 specification and will not process the the calls to
>>> /identity/connect/register which is the endpoint specified in 
>>> OpenIDConnect
>>> specification for DCR. Correct me if I am wrong.
>>>
>>> I would appreciate if you could provide me some more information
>>> regarding exposing an endpoint for the custom component of DCRM.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>>> sor/DCRProcessor.java
>>>
>>> Thank you,
>>> Dinuksha.
>>>
>>> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 Glad to hear that you have made progress with the project.

 As a start, exposing a separate servlet would be okay. But going
 forward with the project, you may have to use the approach used in the 
 DCR
 endpoint which is [1] (or may have to use a cxf endpoint).

 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java

 Thanks,

 On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Devs/Mentors,
>
> This is to inform you the progress made so far with the project.
> In order to get familiar with the wso2 codebase and the product 
> building
> process, 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinukshi,

I will not have time to go through your proposal now. As the deadline is
getting closer, please go ahead and submit the proposal.

Thanks,

On Mon, Apr 3, 2017 at 12:41 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have made the suggested changes in the proposal. Would appreciate if you
> could review and provide feedback.
>
> Thanks,
> Dinuksha.
>
> On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena 
> wrote:
>
>> Hi Dinushika,
>>
>> I have added some comments to the the draft proposal.
>>
>> Thanks,
>>
>> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Sorry for the late reply as I had my Semester exams this week. I have
>>> shared the draft proposal on the GSoC dashboard. Would appreciate if you
>>> could review and provide feedback.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 Thank you for the information. I shall look in to this and proceed with
 the basic implementation and preparing the proposal. Will keep you 
 informed.

 On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinuksha,
>
> DCR has 3 specs.
>
>- OAuth 2.0 Dynamic Client Registration
>- OAuth 2.0 Dynamic Client Registration Management
>- OpenID Connect Dynamic Client Registration
>
> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
> Connect Dynamic Client Registration is handled by [2]. This is the class
> that handles requests for /identity/connect/register. OAuth 2.0
> Dynamic Client Registration Management is the one you are going to
> implement.
>
> As a start you can just register a servlet and implement the
> functionality. We will guide you how to register a processor for identity
> endpoint, if we decide to go in that path.
>
> I hope that I answered your questions. Get back to us of you need
> anything clarified.
>
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
> [2] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
> r/OIDCDCRProcessor.java
>
> Thanks,
>
>
> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I have referred the given code [1] and observed that DCRProcessor
>> will only process requests that call the endpoint /identity/register as
>> OAuth2.0 specification and will not process the the calls to
>> /identity/connect/register which is the endpoint specified in 
>> OpenIDConnect
>> specification for DCR. Correct me if I am wrong.
>>
>> I would appreciate if you could provide me some more information
>> regarding exposing an endpoint for the custom component of DCRM.
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>> sor/DCRProcessor.java
>>
>> Thank you,
>> Dinuksha.
>>
>> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> Glad to hear that you have made progress with the project.
>>>
>>> As a start, exposing a separate servlet would be okay. But going
>>> forward with the project, you may have to use the approach used in the 
>>> DCR
>>> endpoint which is [1] (or may have to use a cxf endpoint).
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>>> sor/DCRProcessor.java
>>>
>>> Thanks,
>>>
>>> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Devs/Mentors,

 This is to inform you the progress made so far with the project. In
 order to get familiar with the wso2 codebase and the product building
 process, I built the kernel and product-is for IS 5.3.0 successfully. 
 Then
 I patched the current DCR component, built it and added as a patch to 
 IS
 and got the modifications applied to the server.

 Now I am working on a basic implementation of the DCRM where I have
 written a separate component and exposed a 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

I have made the suggested changes in the proposal. Would appreciate if you
could review and provide feedback.

Thanks,
Dinuksha.

On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena 
wrote:

> Hi Dinushika,
>
> I have added some comments to the the draft proposal.
>
> Thanks,
>
> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi,
>>
>> Sorry for the late reply as I had my Semester exams this week. I have
>> shared the draft proposal on the GSoC dashboard. Would appreciate if you
>> could review and provide feedback.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> Thank you for the information. I shall look in to this and proceed with
>>> the basic implementation and preparing the proposal. Will keep you informed.
>>>
>>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 DCR has 3 specs.

- OAuth 2.0 Dynamic Client Registration
- OAuth 2.0 Dynamic Client Registration Management
- OpenID Connect Dynamic Client Registration

 OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
 Connect Dynamic Client Registration is handled by [2]. This is the class
 that handles requests for /identity/connect/register. OAuth 2.0
 Dynamic Client Registration Management is the one you are going to
 implement.

 As a start you can just register a servlet and implement the
 functionality. We will guide you how to register a processor for identity
 endpoint, if we decide to go in that path.

 I hope that I answered your questions. Get back to us of you need
 anything clarified.


 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java
 [2] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
 dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
 r/OIDCDCRProcessor.java

 Thanks,


 On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have referred the given code [1] and observed that DCRProcessor will
> only process requests that call the endpoint /identity/register as 
> OAuth2.0
> specification and will not process the the calls to
> /identity/connect/register which is the endpoint specified in 
> OpenIDConnect
> specification for DCR. Correct me if I am wrong.
>
> I would appreciate if you could provide me some more information
> regarding exposing an endpoint for the custom component of DCRM.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
>
> Thank you,
> Dinuksha.
>
> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinuksha,
>>
>> Glad to hear that you have made progress with the project.
>>
>> As a start, exposing a separate servlet would be okay. But going
>> forward with the project, you may have to use the approach used in the 
>> DCR
>> endpoint which is [1] (or may have to use a cxf endpoint).
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>> sor/DCRProcessor.java
>>
>> Thanks,
>>
>> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Devs/Mentors,
>>>
>>> This is to inform you the progress made so far with the project. In
>>> order to get familiar with the wso2 codebase and the product building
>>> process, I built the kernel and product-is for IS 5.3.0 successfully. 
>>> Then
>>> I patched the current DCR component, built it and added as a patch to IS
>>> and got the modifications applied to the server.
>>>
>>> Now I am working on a basic implementation of the DCRM where I have
>>> written a separate component and exposed a servlet from that. I am now
>>> modifying it to accept required parameters and to get the basic flow
>>> working. I will share the code via github soon for reviewing. Meanwhile 
>>> I'm
>>> working on preparing the project proposal as well.
>>>
>>> Regards,
>>> Dinuksha.
>>>
>>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>>> 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinushika,

I have added some comments to the the draft proposal.

Thanks,

On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari  wrote:

> Hi,
>
> Sorry for the late reply as I had my Semester exams this week. I have
> shared the draft proposal on the GSoC dashboard. Would appreciate if you
> could review and provide feedback.
>
> Thanks,
> Dinuksha.
>
> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> Thank you for the information. I shall look in to this and proceed with
>> the basic implementation and preparing the proposal. Will keep you informed.
>>
>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> DCR has 3 specs.
>>>
>>>- OAuth 2.0 Dynamic Client Registration
>>>- OAuth 2.0 Dynamic Client Registration Management
>>>- OpenID Connect Dynamic Client Registration
>>>
>>> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
>>> Connect Dynamic Client Registration is handled by [2]. This is the class
>>> that handles requests for /identity/connect/register. OAuth 2.0 Dynamic
>>> Client Registration Management is the one you are going to implement.
>>>
>>> As a start you can just register a servlet and implement the
>>> functionality. We will guide you how to register a processor for identity
>>> endpoint, if we decide to go in that path.
>>>
>>> I hope that I answered your questions. Get back to us of you need
>>> anything clarified.
>>>
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/
>>> processor/DCRProcessor.java
>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>>> r/OIDCDCRProcessor.java
>>>
>>> Thanks,
>>>
>>>
>>> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 I have referred the given code [1] and observed that DCRProcessor will
 only process requests that call the endpoint /identity/register as OAuth2.0
 specification and will not process the the calls to
 /identity/connect/register which is the endpoint specified in OpenIDConnect
 specification for DCR. Correct me if I am wrong.

 I would appreciate if you could provide me some more information
 regarding exposing an endpoint for the custom component of DCRM.

 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java

 Thank you,
 Dinuksha.

 On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinuksha,
>
> Glad to hear that you have made progress with the project.
>
> As a start, exposing a separate servlet would be okay. But going
> forward with the project, you may have to use the approach used in the DCR
> endpoint which is [1] (or may have to use a cxf endpoint).
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
>
> Thanks,
>
> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Devs/Mentors,
>>
>> This is to inform you the progress made so far with the project. In
>> order to get familiar with the wso2 codebase and the product building
>> process, I built the kernel and product-is for IS 5.3.0 successfully. 
>> Then
>> I patched the current DCR component, built it and added as a patch to IS
>> and got the modifications applied to the server.
>>
>> Now I am working on a basic implementation of the DCRM where I have
>> written a separate component and exposed a servlet from that. I am now
>> modifying it to accept required parameters and to get the basic flow
>> working. I will share the code via github soon for reviewing. Meanwhile 
>> I'm
>> working on preparing the project proposal as well.
>>
>> Regards,
>> Dinuksha.
>>
>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Omindu,
>>>
>>> Thanks for the information.
>>>
>>>
>>>
>>> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera >> > wrote:
>>>
 Hi Dinuksha,

 For OAuth, those two are the only libraries we use.


 On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi,

Sorry for the late reply as I had my Semester exams this week. I have
shared the draft proposal on the GSoC dashboard. Would appreciate if you
could review and provide feedback.

Thanks,
Dinuksha.

On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> Thank you for the information. I shall look in to this and proceed with
> the basic implementation and preparing the proposal. Will keep you informed.
>
> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena  > wrote:
>
>> Hi Dinuksha,
>>
>> DCR has 3 specs.
>>
>>- OAuth 2.0 Dynamic Client Registration
>>- OAuth 2.0 Dynamic Client Registration Management
>>- OpenID Connect Dynamic Client Registration
>>
>> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
>> Connect Dynamic Client Registration is handled by [2]. This is the class
>> that handles requests for /identity/connect/register. OAuth 2.0 Dynamic
>> Client Registration Management is the one you are going to implement.
>>
>> As a start you can just register a servlet and implement the
>> functionality. We will guide you how to register a processor for identity
>> endpoint, if we decide to go in that path.
>>
>> I hope that I answered your questions. Get back to us of you need
>> anything clarified.
>>
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.
>> oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/
>> dcr/processor/DCRProcessor.java
>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/
>> processor/OIDCDCRProcessor.java
>>
>> Thanks,
>>
>>
>> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> I have referred the given code [1] and observed that DCRProcessor will
>>> only process requests that call the endpoint /identity/register as OAuth2.0
>>> specification and will not process the the calls to
>>> /identity/connect/register which is the endpoint specified in OpenIDConnect
>>> specification for DCR. Correct me if I am wrong.
>>>
>>> I would appreciate if you could provide me some more information
>>> regarding exposing an endpoint for the custom component of DCRM.
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>>> sor/DCRProcessor.java
>>>
>>> Thank you,
>>> Dinuksha.
>>>
>>> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 Glad to hear that you have made progress with the project.

 As a start, exposing a separate servlet would be okay. But going
 forward with the project, you may have to use the approach used in the DCR
 endpoint which is [1] (or may have to use a cxf endpoint).

 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java

 Thanks,

 On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Devs/Mentors,
>
> This is to inform you the progress made so far with the project. In
> order to get familiar with the wso2 codebase and the product building
> process, I built the kernel and product-is for IS 5.3.0 successfully. Then
> I patched the current DCR component, built it and added as a patch to IS
> and got the modifications applied to the server.
>
> Now I am working on a basic implementation of the DCRM where I have
> written a separate component and exposed a servlet from that. I am now
> modifying it to accept required parameters and to get the basic flow
> working. I will share the code via github soon for reviewing. Meanwhile 
> I'm
> working on preparing the project proposal as well.
>
> Regards,
> Dinuksha.
>
> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Omindu,
>>
>> Thanks for the information.
>>
>>
>>
>> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
>> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> For OAuth, those two are the only libraries we use.
>>>
>>>
>>> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi,

 When I was going through the code base, I observed that Nimbus and
 Apache Oltu libraries are used for the OAuth2.0 implementation. Could 
 you
 kindly let me know what other libraries are used?

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

Thank you for the information. I shall look in to this and proceed with the
basic implementation and preparing the proposal. Will keep you informed.

On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena 
wrote:

> Hi Dinuksha,
>
> DCR has 3 specs.
>
>- OAuth 2.0 Dynamic Client Registration
>- OAuth 2.0 Dynamic Client Registration Management
>- OpenID Connect Dynamic Client Registration
>
> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
> Connect Dynamic Client Registration is handled by [2]. This is the class
> that handles requests for /identity/connect/register. OAuth 2.0 Dynamic
> Client Registration Management is the one you are going to implement.
>
> As a start you can just register a servlet and implement the
> functionality. We will guide you how to register a processor for identity
> endpoint, if we decide to go in that path.
>
> I hope that I answered your questions. Get back to us of you need anything
> clarified.
>
>
> [1] https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/master/components/org.wso2.carbon.
> identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/
> oauth/dcr/processor/DCRProcessor.java
> [2] https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/master/components/org.wso2.carbon.
> identity.oidc.dcr/src/main/java/org/wso2/carbon/identity/
> oidc/dcr/processor/OIDCDCRProcessor.java
>
> Thanks,
>
>
> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> I have referred the given code [1] and observed that DCRProcessor will
>> only process requests that call the endpoint /identity/register as OAuth2.0
>> specification and will not process the the calls to
>> /identity/connect/register which is the endpoint specified in OpenIDConnect
>> specification for DCR. Correct me if I am wrong.
>>
>> I would appreciate if you could provide me some more information
>> regarding exposing an endpoint for the custom component of DCRM.
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/
>> processor/DCRProcessor.java
>>
>> Thank you,
>> Dinuksha.
>>
>> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> Glad to hear that you have made progress with the project.
>>>
>>> As a start, exposing a separate servlet would be okay. But going forward
>>> with the project, you may have to use the approach used in the DCR endpoint
>>> which is [1] (or may have to use a cxf endpoint).
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/
>>> processor/DCRProcessor.java
>>>
>>> Thanks,
>>>
>>> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Devs/Mentors,

 This is to inform you the progress made so far with the project. In
 order to get familiar with the wso2 codebase and the product building
 process, I built the kernel and product-is for IS 5.3.0 successfully. Then
 I patched the current DCR component, built it and added as a patch to IS
 and got the modifications applied to the server.

 Now I am working on a basic implementation of the DCRM where I have
 written a separate component and exposed a servlet from that. I am now
 modifying it to accept required parameters and to get the basic flow
 working. I will share the code via github soon for reviewing. Meanwhile I'm
 working on preparing the project proposal as well.

 Regards,
 Dinuksha.

 On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Omindu,
>
> Thanks for the information.
>
>
>
> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
> wrote:
>
>> Hi Dinuksha,
>>
>> For OAuth, those two are the only libraries we use.
>>
>>
>> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> When I was going through the code base, I observed that Nimbus and
>>> Apache Oltu libraries are used for the OAuth2.0 implementation. Could 
>>> you
>>> kindly let me know what other libraries are used?
>>>
>>> Thanks,
>>> Dinuksha
>>>
>>>
>>>
>>> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Ishara,

 I have read the OAuth2.0 DCR and DCRM specification and
 familiarized myself with the WSO2 Identity Server DCR implementation. I
 have also written a few blog posts [1][2] in order to share my 
 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

I have referred the given code [1] and observed that DCRProcessor will only
process requests that call the endpoint /identity/register as OAuth2.0
specification and will not process the the calls to
/identity/connect/register which is the endpoint specified in OpenIDConnect
specification for DCR. Correct me if I am wrong.

I would appreciate if you could provide me some more information regarding
exposing an endpoint for the custom component of DCRM.

[1] https://github.com/wso2-extensions/identity-inbound-
auth-oauth/blob/master/components/org.wso2.carbon.
identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/
oauth/dcr/processor/DCRProcessor.java

Thank you,
Dinuksha.

On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena 
wrote:

> Hi Dinuksha,
>
> Glad to hear that you have made progress with the project.
>
> As a start, exposing a separate servlet would be okay. But going forward
> with the project, you may have to use the approach used in the DCR endpoint
> which is [1] (or may have to use a cxf endpoint).
>
> [1] https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/master/components/org.wso2.carbon.
> identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/
> oauth/dcr/processor/DCRProcessor.java
>
> Thanks,
>
> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Devs/Mentors,
>>
>> This is to inform you the progress made so far with the project. In order
>> to get familiar with the wso2 codebase and the product building process, I
>> built the kernel and product-is for IS 5.3.0 successfully. Then I patched
>> the current DCR component, built it and added as a patch to IS and got the
>> modifications applied to the server.
>>
>> Now I am working on a basic implementation of the DCRM where I have
>> written a separate component and exposed a servlet from that. I am now
>> modifying it to accept required parameters and to get the basic flow
>> working. I will share the code via github soon for reviewing. Meanwhile I'm
>> working on preparing the project proposal as well.
>>
>> Regards,
>> Dinuksha.
>>
>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Omindu,
>>>
>>> Thanks for the information.
>>>
>>>
>>>
>>> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
>>> wrote:
>>>
 Hi Dinuksha,

 For OAuth, those two are the only libraries we use.


 On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi,
>
> When I was going through the code base, I observed that Nimbus and
> Apache Oltu libraries are used for the OAuth2.0 implementation. Could you
> kindly let me know what other libraries are used?
>
> Thanks,
> Dinuksha
>
>
>
> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Ishara,
>>
>> I have read the OAuth2.0 DCR and DCRM specification and familiarized
>> myself with the WSO2 Identity Server DCR implementation. I have also
>> written a few blog posts [1][2] in order to share my experience.
>>
>> I would be very much grateful if you could update the jira
>> tickets[3][4] providing more information so that I can attempt to 
>> identify
>> the problem and fix the issue.
>>
>> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
>> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
>> ent-registration.html
>> [3] https://wso2.org/jira/browse/IDENTITY-5184
>> [4] https://wso2.org/jira/browse/IDENTITY-5185
>>
>> Thanks,
>> Dinuksha
>>
>> On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna <
>> isha...@wso2.com> wrote:
>>
>>>
>>>
>>> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>> [+ dev]
>>>
 Hi Ishara,

 Thank you for the information. I'm in the process of reading the
 related specifications and getting familiar with the code base further.
 Will get back to you soon.

 Thanks,
 Dinuksha.

 On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna <
 isha...@wso2.com> wrote:

> Hi Dinuksha,
>
> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
> implementation.
> It’s great  that you have already started working with IS code
> base. Further you can go through current DCR implementation from
> here[1] and go through that code.
>
> You may find open jiras here[2]. Following are related to current
> DCR implementation
> https://wso2.org/jira/browse/IDENTITY-5185
> https://wso2.org/jira/browse/IDENTITY-5184
>
> Thanks,
> Ishara
>

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinuksha,

DCR has 3 specs.

   - OAuth 2.0 Dynamic Client Registration
   - OAuth 2.0 Dynamic Client Registration Management
   - OpenID Connect Dynamic Client Registration

OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID Connect
Dynamic Client Registration is handled by [2]. This is the class that
handles requests for /identity/connect/register. OAuth 2.0 Dynamic Client
Registration Management is the one you are going to implement.

As a start you can just register a servlet and implement the functionality.
We will guide you how to register a processor for identity endpoint, if we
decide to go in that path.

I hope that I answered your questions. Get back to us of you need anything
clarified.


[1]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/processor/DCRProcessor.java
[2]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.oidc.dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processor/OIDCDCRProcessor.java

Thanks,


On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have referred the given code [1] and observed that DCRProcessor will
> only process requests that call the endpoint /identity/register as OAuth2.0
> specification and will not process the the calls to
> /identity/connect/register which is the endpoint specified in OpenIDConnect
> specification for DCR. Correct me if I am wrong.
>
> I would appreciate if you could provide me some more information regarding
> exposing an endpoint for the custom component of DCRM.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.
> oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/
> dcr/processor/DCRProcessor.java
>
> Thank you,
> Dinuksha.
>
> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinuksha,
>>
>> Glad to hear that you have made progress with the project.
>>
>> As a start, exposing a separate servlet would be okay. But going forward
>> with the project, you may have to use the approach used in the DCR endpoint
>> which is [1] (or may have to use a cxf endpoint).
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.
>> oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/
>> dcr/processor/DCRProcessor.java
>>
>> Thanks,
>>
>> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Devs/Mentors,
>>>
>>> This is to inform you the progress made so far with the project. In
>>> order to get familiar with the wso2 codebase and the product building
>>> process, I built the kernel and product-is for IS 5.3.0 successfully. Then
>>> I patched the current DCR component, built it and added as a patch to IS
>>> and got the modifications applied to the server.
>>>
>>> Now I am working on a basic implementation of the DCRM where I have
>>> written a separate component and exposed a servlet from that. I am now
>>> modifying it to accept required parameters and to get the basic flow
>>> working. I will share the code via github soon for reviewing. Meanwhile I'm
>>> working on preparing the project proposal as well.
>>>
>>> Regards,
>>> Dinuksha.
>>>
>>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Omindu,

 Thanks for the information.



 On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
 wrote:

> Hi Dinuksha,
>
> For OAuth, those two are the only libraries we use.
>
>
> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi,
>>
>> When I was going through the code base, I observed that Nimbus and
>> Apache Oltu libraries are used for the OAuth2.0 implementation. Could you
>> kindly let me know what other libraries are used?
>>
>> Thanks,
>> Dinuksha
>>
>>
>>
>> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Ishara,
>>>
>>> I have read the OAuth2.0 DCR and DCRM specification and familiarized
>>> myself with the WSO2 Identity Server DCR implementation. I have also
>>> written a few blog posts [1][2] in order to share my experience.
>>>
>>> I would be very much grateful if you could update the jira
>>> tickets[3][4] providing more information so that I can attempt to 
>>> identify
>>> the problem and fix the issue.
>>>
>>> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell
>>> .html
>>> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
>>> ent-registration.html
>>> [3] 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Devs/Mentors,

This is to inform you the progress made so far with the project. In order
to get familiar with the wso2 codebase and the product building process, I
built the kernel and product-is for IS 5.3.0 successfully. Then I patched
the current DCR component, built it and added as a patch to IS and got the
modifications applied to the server.

Now I am working on a basic implementation of the DCRM where I have written
a separate component and exposed a servlet from that. I am now modifying it
to accept required parameters and to get the basic flow working. I will
share the code via github soon for reviewing. Meanwhile I'm working on
preparing the project proposal as well.

Regards,
Dinuksha.

On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Omindu,
>
> Thanks for the information.
>
>
>
> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
> wrote:
>
>> Hi Dinuksha,
>>
>> For OAuth, those two are the only libraries we use.
>>
>>
>> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> When I was going through the code base, I observed that Nimbus and
>>> Apache Oltu libraries are used for the OAuth2.0 implementation. Could you
>>> kindly let me know what other libraries are used?
>>>
>>> Thanks,
>>> Dinuksha
>>>
>>>
>>>
>>> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Ishara,

 I have read the OAuth2.0 DCR and DCRM specification and familiarized
 myself with the WSO2 Identity Server DCR implementation. I have also
 written a few blog posts [1][2] in order to share my experience.

 I would be very much grateful if you could update the jira
 tickets[3][4] providing more information so that I can attempt to identify
 the problem and fix the issue.

 [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
 [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
 ent-registration.html
 [3] https://wso2.org/jira/browse/IDENTITY-5184
 [4] https://wso2.org/jira/browse/IDENTITY-5185

 Thanks,
 Dinuksha

 On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna  wrote:

>
>
> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
> [+ dev]
>
>> Hi Ishara,
>>
>> Thank you for the information. I'm in the process of reading the
>> related specifications and getting familiar with the code base further.
>> Will get back to you soon.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna <
>> isha...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
>>> implementation.
>>> It’s great  that you have already started working with IS code base.
>>> Further you can go through current DCR implementation from
>>> here[1] and go through that code.
>>>
>>> You may find open jiras here[2]. Following are related to current
>>> DCR implementation
>>> https://wso2.org/jira/browse/IDENTITY-5185
>>> https://wso2.org/jira/browse/IDENTITY-5184
>>>
>>> Thanks,
>>> Ishara
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>>> [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
>>> ?filter=allopenissues
>>>
>>>
>>> On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi All,


 I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri
 Lanka Institute of Information Technology, following the Software
 Engineering specialization.


 This is to convey my interest in implementing the OAuth 2.0
 Dynamic Client Registration Management Protocol Support for
 Identity Server (Proposal 20) in GSoC 2017.


 I am well versed in Java and also familiar with Maven and Git. I
 have been involved in implementing an OAuth 2.0 and OpenID Connect 
 related
 project for almost 7 months during my internship.


 I have already started to get familiar with WSO2 codebase and fixed
 the JIRA [1] where the pull request is already merged to the WSO2 
 codebase.
 I will continue fixing more open JIRA tickets on Identity Server. (If 
 you
 can suggest some, that would be great too)


 In order to get ready for this project, I already setup OAuth 2.0
 Playground2 sample with Identity Server 5.3.0 and wrote the blog post 
 [2]
 for sharing my experience. When running this flow, I faced an issue and
 raised it in the Dev mail [3] and have got 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinuksha,

Glad to hear that you have made progress with the project.

As a start, exposing a separate servlet would be okay. But going forward
with the project, you may have to use the approach used in the DCR endpoint
which is [1] (or may have to use a cxf endpoint).

[1]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.oauth.dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/processor/DCRProcessor.java

Thanks,

On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Devs/Mentors,
>
> This is to inform you the progress made so far with the project. In order
> to get familiar with the wso2 codebase and the product building process, I
> built the kernel and product-is for IS 5.3.0 successfully. Then I patched
> the current DCR component, built it and added as a patch to IS and got the
> modifications applied to the server.
>
> Now I am working on a basic implementation of the DCRM where I have
> written a separate component and exposed a servlet from that. I am now
> modifying it to accept required parameters and to get the basic flow
> working. I will share the code via github soon for reviewing. Meanwhile I'm
> working on preparing the project proposal as well.
>
> Regards,
> Dinuksha.
>
> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Omindu,
>>
>> Thanks for the information.
>>
>>
>>
>> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera 
>> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> For OAuth, those two are the only libraries we use.
>>>
>>>
>>> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi,

 When I was going through the code base, I observed that Nimbus and
 Apache Oltu libraries are used for the OAuth2.0 implementation. Could you
 kindly let me know what other libraries are used?

 Thanks,
 Dinuksha



 On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Ishara,
>
> I have read the OAuth2.0 DCR and DCRM specification and familiarized
> myself with the WSO2 Identity Server DCR implementation. I have also
> written a few blog posts [1][2] in order to share my experience.
>
> I would be very much grateful if you could update the jira
> tickets[3][4] providing more information so that I can attempt to identify
> the problem and fix the issue.
>
> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
> ent-registration.html
> [3] https://wso2.org/jira/browse/IDENTITY-5184
> [4] https://wso2.org/jira/browse/IDENTITY-5185
>
> Thanks,
> Dinuksha
>
> On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna <
> isha...@wso2.com> wrote:
>
>>
>>
>> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>> [+ dev]
>>
>>> Hi Ishara,
>>>
>>> Thank you for the information. I'm in the process of reading the
>>> related specifications and getting familiar with the code base further.
>>> Will get back to you soon.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna <
>>> isha...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 Thank you for your interest in GSoC and the effort on WSO2IS DCRM
 implementation.
 It’s great  that you have already started working with IS code
 base. Further you can go through current DCR implementation from
 here[1] and go through that code.

 You may find open jiras here[2]. Following are related to current
 DCR implementation
 https://wso2.org/jira/browse/IDENTITY-5185
 https://wso2.org/jira/browse/IDENTITY-5184

 Thanks,
 Ishara

 [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
 [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
 ?filter=allopenissues


 On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
>
> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri
> Lanka Institute of Information Technology, following the Software
> Engineering specialization.
>
>
> This is to convey my interest in implementing the OAuth 2.0
> Dynamic Client Registration Management Protocol Support for
> Identity Server (Proposal 20) in GSoC 2017.
>
>
> I am well versed in Java and also familiar with Maven and Git. I
> have been involved in implementing an OAuth 2.0 and OpenID Connect 
> 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Omindu,

Thanks for the information.



On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera  wrote:

> Hi Dinuksha,
>
> For OAuth, those two are the only libraries we use.
>
>
> On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi,
>>
>> When I was going through the code base, I observed that Nimbus and Apache
>> Oltu libraries are used for the OAuth2.0 implementation. Could you kindly
>> let me know what other libraries are used?
>>
>> Thanks,
>> Dinuksha
>>
>>
>>
>> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Ishara,
>>>
>>> I have read the OAuth2.0 DCR and DCRM specification and familiarized
>>> myself with the WSO2 Identity Server DCR implementation. I have also
>>> written a few blog posts [1][2] in order to share my experience.
>>>
>>> I would be very much grateful if you could update the jira tickets[3][4]
>>> providing more information so that I can attempt to identify the problem
>>> and fix the issue.
>>>
>>> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
>>> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
>>> ent-registration.html
>>> [3] https://wso2.org/jira/browse/IDENTITY-5184
>>> [4] https://wso2.org/jira/browse/IDENTITY-5185
>>>
>>> Thanks,
>>> Dinuksha
>>>
>>> On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna 
>>> wrote:
>>>


 On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:
 [+ dev]

> Hi Ishara,
>
> Thank you for the information. I'm in the process of reading the
> related specifications and getting familiar with the code base further.
> Will get back to you soon.
>
> Thanks,
> Dinuksha.
>
> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna <
> isha...@wso2.com> wrote:
>
>> Hi Dinuksha,
>>
>> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
>> implementation.
>> It’s great  that you have already started working with IS code base.
>> Further you can go through current DCR implementation from
>> here[1] and go through that code.
>>
>> You may find open jiras here[2]. Following are related to current DCR
>> implementation
>> https://wso2.org/jira/browse/IDENTITY-5185
>> https://wso2.org/jira/browse/IDENTITY-5184
>>
>> Thanks,
>> Ishara
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>> [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
>> ?filter=allopenissues
>>
>>
>> On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>>
>>> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri
>>> Lanka Institute of Information Technology, following the Software
>>> Engineering specialization.
>>>
>>>
>>> This is to convey my interest in implementing the OAuth 2.0 Dynamic
>>> Client Registration Management Protocol Support for Identity Server
>>> (Proposal 20) in GSoC 2017.
>>>
>>>
>>> I am well versed in Java and also familiar with Maven and Git. I
>>> have been involved in implementing an OAuth 2.0 and OpenID Connect 
>>> related
>>> project for almost 7 months during my internship.
>>>
>>>
>>> I have already started to get familiar with WSO2 codebase and fixed
>>> the JIRA [1] where the pull request is already merged to the WSO2 
>>> codebase.
>>> I will continue fixing more open JIRA tickets on Identity Server. (If 
>>> you
>>> can suggest some, that would be great too)
>>>
>>>
>>> In order to get ready for this project, I already setup OAuth 2.0
>>> Playground2 sample with Identity Server 5.3.0 and wrote the blog post 
>>> [2]
>>> for sharing my experience. When running this flow, I faced an issue and
>>> raised it in the Dev mail [3] and have got the answer now.
>>>
>>>
>>> My GitHub profile can be found at [4].
>>>
>>>
>>> Therefore I believe I can learn the required concepts/technologies
>>> and implement this project for GSoC 2017.
>>>
>>>
>>> I appreciate if you can guide me on proceeding further with the
>>> project.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-5241
>>>
>>> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-with
>>> -oauth-20-using.html
>>>
>>> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>>>
>>> [4] https://github.com/dinuish94
>>>
>>>
>>> Best Regards,
>>>
>>> Dinuksha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ishara Karunarathna

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Omindu Rathnaweera]

Hi Dinuksha,

For OAuth, those two are the only libraries we use.


On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi,
>
> When I was going through the code base, I observed that Nimbus and Apache
> Oltu libraries are used for the OAuth2.0 implementation. Could you kindly
> let me know what other libraries are used?
>
> Thanks,
> Dinuksha
>
>
>
> On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Ishara,
>>
>> I have read the OAuth2.0 DCR and DCRM specification and familiarized
>> myself with the WSO2 Identity Server DCR implementation. I have also
>> written a few blog posts [1][2] in order to share my experience.
>>
>> I would be very much grateful if you could update the jira tickets[3][4]
>> providing more information so that I can attempt to identify the problem
>> and fix the issue.
>>
>> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
>> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-cli
>> ent-registration.html
>> [3] https://wso2.org/jira/browse/IDENTITY-5184
>> [4] https://wso2.org/jira/browse/IDENTITY-5185
>>
>> Thanks,
>> Dinuksha
>>
>> On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna 
>> wrote:
>>
>>>
>>>
>>> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>> [+ dev]
>>>
 Hi Ishara,

 Thank you for the information. I'm in the process of reading the
 related specifications and getting familiar with the code base further.
 Will get back to you soon.

 Thanks,
 Dinuksha.

 On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna  wrote:

> Hi Dinuksha,
>
> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
> implementation.
> It’s great  that you have already started working with IS code base.
> Further you can go through current DCR implementation from
> here[1] and go through that code.
>
> You may find open jiras here[2]. Following are related to current DCR
> implementation
> https://wso2.org/jira/browse/IDENTITY-5185
> https://wso2.org/jira/browse/IDENTITY-5184
>
> Thanks,
> Ishara
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
> [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
> ?filter=allopenissues
>
>
> On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi All,
>>
>>
>> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
>> Institute of Information Technology, following the Software Engineering
>> specialization.
>>
>>
>> This is to convey my interest in implementing the OAuth 2.0 Dynamic
>> Client Registration Management Protocol Support for Identity Server
>> (Proposal 20) in GSoC 2017.
>>
>>
>> I am well versed in Java and also familiar with Maven and Git. I have
>> been involved in implementing an OAuth 2.0 and OpenID Connect related
>> project for almost 7 months during my internship.
>>
>>
>> I have already started to get familiar with WSO2 codebase and fixed
>> the JIRA [1] where the pull request is already merged to the WSO2 
>> codebase.
>> I will continue fixing more open JIRA tickets on Identity Server. (If you
>> can suggest some, that would be great too)
>>
>>
>> In order to get ready for this project, I already setup OAuth 2.0
>> Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
>> for sharing my experience. When running this flow, I faced an issue and
>> raised it in the Dev mail [3] and have got the answer now.
>>
>>
>> My GitHub profile can be found at [4].
>>
>>
>> Therefore I believe I can learn the required concepts/technologies
>> and implement this project for GSoC 2017.
>>
>>
>> I appreciate if you can guide me on proceeding further with the
>> project.
>>
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-5241
>>
>> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-with
>> -oauth-20-using.html
>>
>> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>>
>> [4] https://github.com/dinuish94
>>
>>
>> Best Regards,
>>
>> Dinuksha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>

>>>
>>>
>>> --
>>> Ishara Karunarathna
>>> Associate Technical 

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi,

When I was going through the code base, I observed that Nimbus and Apache
Oltu libraries are used for the OAuth2.0 implementation. Could you kindly
let me know what other libraries are used?

Thanks,
Dinuksha



On Mon, Feb 27, 2017 at 9:51 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi Ishara,
>
> I have read the OAuth2.0 DCR and DCRM specification and familiarized
> myself with the WSO2 Identity Server DCR implementation. I have also
> written a few blog posts [1][2] in order to share my experience.
>
> I would be very much grateful if you could update the jira tickets[3][4]
> providing more information so that I can attempt to identify the problem
> and fix the issue.
>
> [1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
> [2] http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-
> client-registration.html
> [3] https://wso2.org/jira/browse/IDENTITY-5184
> [4] https://wso2.org/jira/browse/IDENTITY-5185
>
> Thanks,
> Dinuksha
>
> On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna 
> wrote:
>
>>
>>
>> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>> [+ dev]
>>
>>> Hi Ishara,
>>>
>>> Thank you for the information. I'm in the process of reading the related
>>> specifications and getting familiar with the code base further. Will get
>>> back to you soon.
>>>
>>> Thanks,
>>> Dinuksha.
>>>
>>> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna 
>>> wrote:
>>>
 Hi Dinuksha,

 Thank you for your interest in GSoC and the effort on WSO2IS DCRM
 implementation.
 It’s great  that you have already started working with IS code base.
 Further you can go through current DCR implementation from
 here[1] and go through that code.

 You may find open jiras here[2]. Following are related to current DCR
 implementation
 https://wso2.org/jira/browse/IDENTITY-5185
 https://wso2.org/jira/browse/IDENTITY-5184

 Thanks,
 Ishara

 [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
 [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
 ?filter=allopenissues


 On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
>
> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
> Institute of Information Technology, following the Software Engineering
> specialization.
>
>
> This is to convey my interest in implementing the OAuth 2.0 Dynamic
> Client Registration Management Protocol Support for Identity Server
> (Proposal 20) in GSoC 2017.
>
>
> I am well versed in Java and also familiar with Maven and Git. I have
> been involved in implementing an OAuth 2.0 and OpenID Connect related
> project for almost 7 months during my internship.
>
>
> I have already started to get familiar with WSO2 codebase and fixed
> the JIRA [1] where the pull request is already merged to the WSO2 
> codebase.
> I will continue fixing more open JIRA tickets on Identity Server. (If you
> can suggest some, that would be great too)
>
>
> In order to get ready for this project, I already setup OAuth 2.0
> Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
> for sharing my experience. When running this flow, I faced an issue and
> raised it in the Dev mail [3] and have got the answer now.
>
>
> My GitHub profile can be found at [4].
>
>
> Therefore I believe I can learn the required concepts/technologies and
> implement this project for GSoC 2017.
>
>
> I appreciate if you can guide me on proceeding further with the
> project.
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-5241
>
> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-with
> -oauth-20-using.html
>
> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>
> [4] https://github.com/dinuish94
>
>
> Best Regards,
>
> Dinuksha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
 +94717996791 <+94%2071%20799%206791>



>>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <+94%2071%20799%206791>
>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Ishara,

I have read the OAuth2.0 DCR and DCRM specification and familiarized myself
with the WSO2 Identity Server DCR implementation. I have also written a few
blog posts [1][2] in order to share my experience.

I would be very much grateful if you could update the jira tickets[3][4]
providing more information so that I can attempt to identify the problem
and fix the issue.

[1] http://dinukshaish.blogspot.com/2017/02/oauth-20-in-nutshell.html
[2]
http://dinukshaish.blogspot.com/2017/02/oauth-20-dynamic-client-registration.html
[3] https://wso2.org/jira/browse/IDENTITY-5184
[4] https://wso2.org/jira/browse/IDENTITY-5185

Thanks,
Dinuksha

On Fri, Feb 24, 2017 at 11:53 AM, Ishara Karunarathna 
wrote:

>
>
> On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
> [+ dev]
>
>> Hi Ishara,
>>
>> Thank you for the information. I'm in the process of reading the related
>> specifications and getting familiar with the code base further. Will get
>> back to you soon.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna 
>> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
>>> implementation.
>>> It’s great  that you have already started working with IS code base.
>>> Further you can go through current DCR implementation from
>>> here[1] and go through that code.
>>>
>>> You may find open jiras here[2]. Following are related to current DCR
>>> implementation
>>> https://wso2.org/jira/browse/IDENTITY-5185
>>> https://wso2.org/jira/browse/IDENTITY-5184
>>>
>>> Thanks,
>>> Ishara
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>>> [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723
>>> ?filter=allopenissues
>>>
>>>
>>> On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi All,


 I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
 Institute of Information Technology, following the Software Engineering
 specialization.


 This is to convey my interest in implementing the OAuth 2.0 Dynamic
 Client Registration Management Protocol Support for Identity Server
 (Proposal 20) in GSoC 2017.


 I am well versed in Java and also familiar with Maven and Git. I have
 been involved in implementing an OAuth 2.0 and OpenID Connect related
 project for almost 7 months during my internship.


 I have already started to get familiar with WSO2 codebase and fixed the
 JIRA [1] where the pull request is already merged to the WSO2 codebase. I
 will continue fixing more open JIRA tickets on Identity Server. (If you can
 suggest some, that would be great too)


 In order to get ready for this project, I already setup OAuth 2.0
 Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
 for sharing my experience. When running this flow, I faced an issue and
 raised it in the Dev mail [3] and have got the answer now.


 My GitHub profile can be found at [4].


 Therefore I believe I can learn the required concepts/technologies and
 implement this project for GSoC 2017.


 I appreciate if you can guide me on proceeding further with the project.


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

 [2] http://dinukshaish.blogspot.com/2017/02/getting-started-with
 -oauth-20-using.html

 [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0

 [4] https://github.com/dinuish94


 Best Regards,

 Dinuksha

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


>>>
>>>
>>> --
>>> Ishara Karunarathna
>>> Associate Technical Lead
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>>> +94717996791 <+94%2071%20799%206791>
>>>
>>>
>>>
>>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791 <+94%2071%20799%206791>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Ishara Karunarathna]

On Fri, Feb 24, 2017 at 11:16 AM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:
[+ dev]

> Hi Ishara,
>
> Thank you for the information. I'm in the process of reading the related
> specifications and getting familiar with the code base further. Will get
> back to you soon.
>
> Thanks,
> Dinuksha.
>
> On Fri, Feb 24, 2017 at 10:14 AM, Ishara Karunarathna 
> wrote:
>
>> Hi Dinuksha,
>>
>> Thank you for your interest in GSoC and the effort on WSO2IS DCRM
>> implementation.
>> It’s great  that you have already started working with IS code base.
>> Further you can go through current DCR implementation from
>> here[1] and go through that code.
>>
>> You may find open jiras here[2]. Following are related to current DCR
>> implementation
>> https://wso2.org/jira/browse/IDENTITY-5185
>> https://wso2.org/jira/browse/IDENTITY-5184
>>
>> Thanks,
>> Ishara
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
>> [2] https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-
>> 5723?filter=allopenissues
>>
>>
>> On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>>
>>> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
>>> Institute of Information Technology, following the Software Engineering
>>> specialization.
>>>
>>>
>>> This is to convey my interest in implementing the OAuth 2.0 Dynamic
>>> Client Registration Management Protocol Support for Identity Server
>>> (Proposal 20) in GSoC 2017.
>>>
>>>
>>> I am well versed in Java and also familiar with Maven and Git. I have
>>> been involved in implementing an OAuth 2.0 and OpenID Connect related
>>> project for almost 7 months during my internship.
>>>
>>>
>>> I have already started to get familiar with WSO2 codebase and fixed the
>>> JIRA [1] where the pull request is already merged to the WSO2 codebase. I
>>> will continue fixing more open JIRA tickets on Identity Server. (If you can
>>> suggest some, that would be great too)
>>>
>>>
>>> In order to get ready for this project, I already setup OAuth 2.0
>>> Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
>>> for sharing my experience. When running this flow, I faced an issue and
>>> raised it in the Dev mail [3] and have got the answer now.
>>>
>>>
>>> My GitHub profile can be found at [4].
>>>
>>>
>>> Therefore I believe I can learn the required concepts/technologies and
>>> implement this project for GSoC 2017.
>>>
>>>
>>> I appreciate if you can guide me on proceeding further with the project.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-5241
>>>
>>> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-with
>>> -oauth-20-using.html
>>>
>>> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>>>
>>> [4] https://github.com/dinuish94
>>>
>>>
>>> Best Regards,
>>>
>>> Dinuksha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791 <+94%2071%20799%206791>
>>
>>
>>
>


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

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

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Ishara Karunarathna]

Hi Dinuksha,

Thank you for your interest in GSoC and the effort on WSO2IS DCRM
implementation.
It’s great  that you have already started working with IS code base.
Further you can go through current DCR implementation from
here[1] and go through that code.

You may find open jiras here[2]. Following are related to current DCR
implementation
https://wso2.org/jira/browse/IDENTITY-5185
https://wso2.org/jira/browse/IDENTITY-5184

Thanks,
Ishara

[1] https://github.com/wso2-extensions/identity-inbound-auth-oauth
[2]
https://wso2.org/jira/projects/IDENTITY/issues/IDENTITY-5723?filter=allopenissues


On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
>
> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
> Institute of Information Technology, following the Software Engineering
> specialization.
>
>
> This is to convey my interest in implementing the OAuth 2.0 Dynamic
> Client Registration Management Protocol Support for Identity Server
> (Proposal 20) in GSoC 2017.
>
>
> I am well versed in Java and also familiar with Maven and Git. I have been
> involved in implementing an OAuth 2.0 and OpenID Connect related project
> for almost 7 months during my internship.
>
>
> I have already started to get familiar with WSO2 codebase and fixed the
> JIRA [1] where the pull request is already merged to the WSO2 codebase. I
> will continue fixing more open JIRA tickets on Identity Server. (If you can
> suggest some, that would be great too)
>
>
> In order to get ready for this project, I already setup OAuth 2.0
> Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
> for sharing my experience. When running this flow, I faced an issue and
> raised it in the Dev mail [3] and have got the answer now.
>
>
> My GitHub profile can be found at [4].
>
>
> Therefore I believe I can learn the required concepts/technologies and
> implement this project for GSoC 2017.
>
>
> I appreciate if you can guide me on proceeding further with the project.
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-5241
>
> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-
> with-oauth-20-using.html
>
> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>
> [4] https://github.com/dinuish94
>
>
> Best Regards,
>
> Dinuksha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Omindu Rathnaweera]

Adding project mentors.

On Mon, Feb 20, 2017 at 4:45 PM, Dinuksha Ishwari <
dinuksha.ishw...@gmail.com> wrote:

> Hi All,
>
>
> I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
> Institute of Information Technology, following the Software Engineering
> specialization.
>
>
> This is to convey my interest in implementing the OAuth 2.0 Dynamic
> Client Registration Management Protocol Support for Identity Server
> (Proposal 20) in GSoC 2017.
>
>
> I am well versed in Java and also familiar with Maven and Git. I have been
> involved in implementing an OAuth 2.0 and OpenID Connect related project
> for almost 7 months during my internship.
>
>
> I have already started to get familiar with WSO2 codebase and fixed the
> JIRA [1] where the pull request is already merged to the WSO2 codebase. I
> will continue fixing more open JIRA tickets on Identity Server. (If you can
> suggest some, that would be great too)
>
>
> In order to get ready for this project, I already setup OAuth 2.0
> Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
> for sharing my experience. When running this flow, I faced an issue and
> raised it in the Dev mail [3] and have got the answer now.
>
>
> My GitHub profile can be found at [4].
>
>
> Therefore I believe I can learn the required concepts/technologies and
> implement this project for GSoC 2017.
>
>
> I appreciate if you can guide me on proceeding further with the project.
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-5241
>
> [2] http://dinukshaish.blogspot.com/2017/02/getting-started-
> with-oauth-20-using.html
>
> [3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0
>
> [4] https://github.com/dinuish94
>
>
> Best Regards,
>
> Dinuksha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Omindu Rathnaweera
Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi All,


I am Dinuksha Kanda Samanage, a 3rd year undergraduate from Sri Lanka
Institute of Information Technology, following the Software Engineering
specialization.


This is to convey my interest in implementing the OAuth 2.0 Dynamic Client
Registration Management Protocol Support for Identity Server (Proposal 20)
in GSoC 2017.


I am well versed in Java and also familiar with Maven and Git. I have been
involved in implementing an OAuth 2.0 and OpenID Connect related project
for almost 7 months during my internship.


I have already started to get familiar with WSO2 codebase and fixed the
JIRA [1] where the pull request is already merged to the WSO2 codebase. I
will continue fixing more open JIRA tickets on Identity Server. (If you can
suggest some, that would be great too)


In order to get ready for this project, I already setup OAuth 2.0
Playground2 sample with Identity Server 5.3.0 and wrote the blog post [2]
for sharing my experience. When running this flow, I faced an issue and
raised it in the Dev mail [3] and have got the answer now.


My GitHub profile can be found at [4].


Therefore I believe I can learn the required concepts/technologies and
implement this project for GSoC 2017.


I appreciate if you can guide me on proceeding further with the project.


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

[2]
http://dinukshaish.blogspot.com/2017/02/getting-started-with-oauth-20-using.html

[3] [Dev] Mandatory Claims in OAuth 2.0 with Identity Server 5.3.0

[4] https://github.com/dinuish94


Best Regards,

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