On Thu, Aug 31, 2017 at 12:12 AM, Vindula Jayawardana < [email protected]> wrote:
> Hi, > > IMO, should be able to enable both at the same time. What is the issue you > faced when enabling both? > > Achieving interoperability between 1.1 consumers and 2.0 providers can > have two practical approaches. One approach is to have a multi-protocol > ability in the SCIM service provider’s end. This could be potentially done > through unique URL structure (https://localhost:9443/wso2/scim/Users and > https://localhost:9443/scim2/Users). That means the provider can accept > both 1.1 and 2.0 consumers. On the other hand, SCIM consumer can be > modified to support the 1.1 and 2.0 protocols. However, since SCIM > specifications are focusing on keeping things simple and easy at the > consumer end, I would rather suggest the first approach. That’s why we > should be able to enable both the protocols at the same time. > > *Vindula Jayawardana* > Computer Science and Engineering Dept. > University of Moratuwa > mobile : +713462554 > Email : [email protected] > > <https://www.facebook.com/vindula.jayawardana> > <http://lk.linkedin.com/pub/vindula-jayawardana/a7/315/53b> > <https://plus.google.com/u/0/+VindulaJayawardana/posts> > <https://twitter.com/vindulajay> > > *“Respect is how to treat everyone, not just those you want to impress. "* > > > *-Richard Branson-* > > > > On 30 August 2017 at 18:33, Sathya Bandara <[email protected]> wrote: > >> Hi Thilina, >> >> If we enable both SCIM1 and SCIM2 listeners at the same time two >> different SCIM IDs will be generated for the same user when adding a new >> user through SCIM. Also both SCIM1 and SCIM2 claims are mapped to the same >> LDAP user attributes. Even though both listeners get triggered only the >> SCIM1 ID is mapped to the user ID attribute. But the SCIM2 user creation >> response will contain the SCIM ID generated by SCIM2 listener. >> > This is not a SCIM related problem instead a limitation of our implementation, SCIM is just a interface or wrapping layer for our user/role management layer. Ideally it should not perform tasks such as ID generation by it's own, instead once the SCIM protocol specific processing is completed both SCIM1 and SCIM2 implementations should delegate requests into a common layer, in that way we can provide interoperability between SCIM1 and SCIM2. +1 for Vindula's suggestion on multi-protocol approach. Thanks ! > >> Thanks, >> Sathya >> >> On Wed, Aug 30, 2017 at 6:25 PM, Thilina Madumal <[email protected]> >> wrote: >> >>> >>> Hi all, >>> >>> While I was trying to fix IDENTITY-6315 >>> <https://wso2.org/jira/browse/IDENTITY-6315> I got to know that we >>> can't enable both SCIM1 and SCIM2 at the same time in WSO2 Identity Server. >>> Is it because of this specific issue or is there any other reasons? >>> >>> Thanks & Regards, >>> Thilina. >>> >>> -- >>> *Thilina Madumal* >>> *Software Engineer | **WSO2* >>> Email: [email protected] >>> Mobile: *+ <+94%2077%20767%201807>94 774553167* >>> Web: <http://goog_716986954>http://wso2.com >>> >>> <http://wso2.com/signature> >>> >>> >> >> >> -- >> Sathya Bandara >> Software Engineer >> WSO2 Inc. http://wso2.com >> Mobile: (+94) 715 360 421 <+94%2071%20411%205032> >> >> <+94%2071%20411%205032> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sagara Gunathunga Associate Director / Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
