Re: [Carbon-dev] ApacheDS as default user store of core ?
Big +1 to your proposal. Paul On 3 January 2012 11:35, Amila Jayasekara wrote: > On Tue, Jan 3, 2012 at 4:07 PM, Paul Fremantle wrote: > > Is there any other difference betwee ApacheDS embedded and H2? In > general I > > think that what you have suggested is the right way forward, but I want > to > > check what else? > > Hi Paul, > > Following are some other differences between ApacheDS and "Embedded H2". > 1. ApacheDS has an internal KDC server. By default this is disabled. > (It is enabled only for IS). But can be enable using a configuration > change and run a KDC server in other products also. > 2. "Embedded H2" allows a single client connection, but multiple > clients can connect to ApacheDS > 3. ApacheDS adds about 7.4 MB to distribution size > > Thanks > AmilaJ > > > > > > Paul > > > > On 28 June 2011 07:27, Amila Jayasekara wrote: > >> > >> Hi All, > >> > >> It seems that lot of members were under the impression that embedded > >> LDAP server is not binding an address. Thus most of the people are > >> under the impression that it behaves like H2. But this is not the > >> case. > >> > >> We (me, Shankar, Amila and Azeez) had a discussion about this. > >> As per our current implementation we have LDAP servers embedded in all > >> products. Also it seems having LDAP servers in all products is not > >> architecturally sound. > >> > >> Thus apacheds has a way of by passing the network layer and using just > >> like H2. For this we need to write a new user store manager. But IMO > >> we are not going to gain much from implementing a user store manager > >> which uses only apacheds (By passing network layer). Instead we could > >> use H2. > >> > >> So the conclusion was to use apacheds only within Identity Server and > >> make it an optional feature for other products. Other products will > >> use H2 as it was used to be. > >> > >> Please let us know what you all think about this conclusion. > >> > >> Feedback appreciated. > >> > >> Thanks > >> AmilaJ > >> ___ > >> Carbon-dev mailing list > >> Carbon-dev@wso2.org > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > > > -- > > Paul Fremantle > > CTO and Co-Founder, WSO2 > > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > > > UK: +44 207 096 0336 > > US: +1 646 595 7614 > > > > blog: http://pzf.fremantle.org > > twitter.com/pzfreo > > p...@wso2.com > > > > wso2.com Lean Enterprise Middleware > > > > Disclaimer: This communication may contain privileged or other > confidential > > information and is intended exclusively for the addressee/s. If you are > not > > the intended recipient/s, or believe that you may have received this > > communication in error, please reply to the sender indicating that fact > and > > delete the copy you received and in addition, you should not print, copy, > > retransmit, disseminate, or otherwise use the information contained in > this > > communication. Internet communications cannot be guaranteed to be timely, > > secure, error or virus-free. The sender does not accept liability for any > > errors or omissions. > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > -- > Mobile : +94773330538 > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ApacheDS as default user store of core ?
On Tue, Jan 3, 2012 at 4:07 PM, Paul Fremantle wrote: > Is there any other difference betwee ApacheDS embedded and H2? In general I > think that what you have suggested is the right way forward, but I want to > check what else? Hi Paul, Following are some other differences between ApacheDS and "Embedded H2". 1. ApacheDS has an internal KDC server. By default this is disabled. (It is enabled only for IS). But can be enable using a configuration change and run a KDC server in other products also. 2. "Embedded H2" allows a single client connection, but multiple clients can connect to ApacheDS 3. ApacheDS adds about 7.4 MB to distribution size Thanks AmilaJ > > Paul > > On 28 June 2011 07:27, Amila Jayasekara wrote: >> >> Hi All, >> >> It seems that lot of members were under the impression that embedded >> LDAP server is not binding an address. Thus most of the people are >> under the impression that it behaves like H2. But this is not the >> case. >> >> We (me, Shankar, Amila and Azeez) had a discussion about this. >> As per our current implementation we have LDAP servers embedded in all >> products. Also it seems having LDAP servers in all products is not >> architecturally sound. >> >> Thus apacheds has a way of by passing the network layer and using just >> like H2. For this we need to write a new user store manager. But IMO >> we are not going to gain much from implementing a user store manager >> which uses only apacheds (By passing network layer). Instead we could >> use H2. >> >> So the conclusion was to use apacheds only within Identity Server and >> make it an optional feature for other products. Other products will >> use H2 as it was used to be. >> >> Please let us know what you all think about this conclusion. >> >> Feedback appreciated. >> >> Thanks >> AmilaJ >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ApacheDS as default user store of core ?
Is there any other difference betwee ApacheDS embedded and H2? In general I think that what you have suggested is the right way forward, but I want to check what else? Paul On 28 June 2011 07:27, Amila Jayasekara wrote: > Hi All, > > It seems that lot of members were under the impression that embedded > LDAP server is not binding an address. Thus most of the people are > under the impression that it behaves like H2. But this is not the > case. > > We (me, Shankar, Amila and Azeez) had a discussion about this. > As per our current implementation we have LDAP servers embedded in all > products. Also it seems having LDAP servers in all products is not > architecturally sound. > > Thus apacheds has a way of by passing the network layer and using just > like H2. For this we need to write a new user store manager. But IMO > we are not going to gain much from implementing a user store manager > which uses only apacheds (By passing network layer). Instead we could > use H2. > > So the conclusion was to use apacheds only within Identity Server and > make it an optional feature for other products. Other products will > use H2 as it was used to be. > > Please let us know what you all think about this conclusion. > > Feedback appreciated. > > Thanks > AmilaJ > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ApacheDS as default user store of core ?
On Tue, Jan 3, 2012 at 3:33 PM, Manjula Rathnayake wrote: > Hi all, > > I will move apacheds component/feature from carbon core to components. > This way we can avoid embeded ldap server within all products and add the > feature only to identity server. > > If you have no concern on this, I will move on. > +1. Thanks, Thilina > > Thank you. > > On Tue, Jun 28, 2011 at 11:57 AM, Amila Jayasekara wrote: > >> Hi All, >> >> It seems that lot of members were under the impression that embedded >> LDAP server is not binding an address. Thus most of the people are >> under the impression that it behaves like H2. But this is not the >> case. >> >> We (me, Shankar, Amila and Azeez) had a discussion about this. >> As per our current implementation we have LDAP servers embedded in all >> products. Also it seems having LDAP servers in all products is not >> architecturally sound. >> >> Thus apacheds has a way of by passing the network layer and using just >> like H2. For this we need to write a new user store manager. But IMO >> we are not going to gain much from implementing a user store manager >> which uses only apacheds (By passing network layer). Instead we could >> use H2. >> >> So the conclusion was to use apacheds only within Identity Server and >> make it an optional feature for other products. Other products will >> use H2 as it was used to be. >> >> Please let us know what you all think about this conclusion. >> >> Feedback appreciated. >> >> Thanks >> AmilaJ >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Manjula Rathnayaka > Software Engineer > WSO2, Inc. > Mobile:+94 77 743 1987 > -- Thilina Buddhika Associate Technical Lead WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 77 44 88 727 blog : http://blog.thilinamb.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] ApacheDS as default user store of core ?
Hi all, I will move apacheds component/feature from carbon core to components. This way we can avoid embeded ldap server within all products and add the feature only to identity server. If you have no concern on this, I will move on. Thank you. On Tue, Jun 28, 2011 at 11:57 AM, Amila Jayasekara wrote: > Hi All, > > It seems that lot of members were under the impression that embedded > LDAP server is not binding an address. Thus most of the people are > under the impression that it behaves like H2. But this is not the > case. > > We (me, Shankar, Amila and Azeez) had a discussion about this. > As per our current implementation we have LDAP servers embedded in all > products. Also it seems having LDAP servers in all products is not > architecturally sound. > > Thus apacheds has a way of by passing the network layer and using just > like H2. For this we need to write a new user store manager. But IMO > we are not going to gain much from implementing a user store manager > which uses only apacheds (By passing network layer). Instead we could > use H2. > > So the conclusion was to use apacheds only within Identity Server and > make it an optional feature for other products. Other products will > use H2 as it was used to be. > > Please let us know what you all think about this conclusion. > > Feedback appreciated. > > Thanks > AmilaJ > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] ApacheDS as default user store of core ?
Hi All, It seems that lot of members were under the impression that embedded LDAP server is not binding an address. Thus most of the people are under the impression that it behaves like H2. But this is not the case. We (me, Shankar, Amila and Azeez) had a discussion about this. As per our current implementation we have LDAP servers embedded in all products. Also it seems having LDAP servers in all products is not architecturally sound. Thus apacheds has a way of by passing the network layer and using just like H2. For this we need to write a new user store manager. But IMO we are not going to gain much from implementing a user store manager which uses only apacheds (By passing network layer). Instead we could use H2. So the conclusion was to use apacheds only within Identity Server and make it an optional feature for other products. Other products will use H2 as it was used to be. Please let us know what you all think about this conclusion. Feedback appreciated. Thanks AmilaJ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
