On 04/04/2018 16:07, Isuranga Perera wrote:

I would like to work on SYNCOPE-1219. But it has GSoC 2018 tag. So is it okay to work on that.

SYNCOPE-1219 has received no proposals for GSoC.
Feature-wise, it's exactly as SYNCOPE-1220 (which is for Netbeans, instead).

It would be great if you can review the current Eclipse plugin, polish if needed and add support for Groovy implementations.

In the meanwhile, you might want to do some paperwork:


by sending your ICLA.

Finally, consider that Groovy implementations are only available in the master branch, so you should work there.


On Wed, Apr 4, 2018 at 4:47 PM, Francesco Chicchiriccò <ilgro...@apache.org <mailto:ilgro...@apache.org>> wrote:

    I can see a couple of issues in JIRA waiting for someone to pick up:

    * https://issues.apache.org/jira/browse/SYNCOPE-1019
    * https://issues.apache.org/jira/browse/SYNCOPE-1219

    Unfortunately, none is related to the competences mentioned below,
    but maybe you can take them into account.


    On 04/04/2018 09:27, Isuranga Perera wrote:

        Hi Francesco,

        Can you suggest a feature I can work on. I've previously
        worked in OpenID Connect, SAML, SCIM and XACML projects. So
        appreciate if you can suggest a feature/issue that I can work on.

        Best Regards
        Isuranga Perera

        On Tue, Apr 3, 2018 at 4:31 PM, Dima Ayash
        <dima.ay...@tirasa.net <mailto:dima.ay...@tirasa.net>
        <mailto:dima.ay...@tirasa.net <mailto:dima.ay...@tirasa.net>>>


            Thank you for your interest.
            The work has been done until now regarding this feature is:
            •The authorization code flow is the flow that is used for and
            "Google" as an example for the OpenID Provider.
            •To configure the OpenID Provider metadata to apply this flow,
            there are two ways depends on what the OpenID Provider
            in case of supporting the Discovery  Document, requesting this
            document and process the response and stored the required
            otherwise the user needs to insert these values.
            •The work used CXF OIDC dependency, and took benefits from the
            structure of SAML2.0 feature.
            •The work is still under progress, the core and the logic
        of the
            flow is done and tested, the user can have a session by
            successfully to his account in "Google" and by having a
        user in
            Apache Syncope.

            I would really appreciate questions for more details and
        also more
            suggestions to enhance this work.

            Thank you in advance and best regards,
            Dima Ayash.

            ----- Original Message -----
            From: "Francesco Chicchiriccò" <ilgro...@apache.org
            <mailto:ilgro...@apache.org <mailto:ilgro...@apache.org>>>
            To: dev@syncope.apache.org <mailto:dev@syncope.apache.org>
        <mailto:dev@syncope.apache.org <mailto:dev@syncope.apache.org>>
            Sent: Tuesday, April 3, 2018 8:54:00 AM
            Subject: Re: SYNCOPE-1270 : OpenID Connect client feature

            On 03/04/2018 06:39, Isuranga Perera wrote:
            > Hi All,
            > I would like to contribute $subject. I have contributed
        to WSO2
            > server and have worked with OpenID Connect and its profiles.
            Appreciate if
            > someone can provide me guidance throughout this feature.
            > Best Regards
            > Isuranga Perera

            Dear Isuranga,
            thanks for your interest in Apache Syncope.

            As far as we know, there is already someone at work on the
        topic: see


            Maybe you can pick one of the other feature requests from
        JIRA, or
            propose a new one.

            @Dima: could it be possible to provide a status update
        about your work


Francesco Chicchiriccò

Tirasa - Open Source Excellence

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail

Reply via email to