http://blogs.kuppingercole.com/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/ Kuppinger Cole Fri, 04 May 2012 06:56:02 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://blogs.kuppingercole.com/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/comment-page-1/#comment-126 bernie Mon, 02 Nov 2009 22:03:44 +0000 http://blogs.kuppingercole.de/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/#comment-126 Is there any technical documentation of how Apertio's One-NDS works/implemented? How easy is it to convert a traditional LDAP server e.g. OpenLDAP to function as close as possible to Apertio's One-NDS? Is there any technical documentation of how Apertio's One-NDS works/implemented? How easy is it to convert a traditional LDAP server e.g. OpenLDAP to function as close as possible to Apertio's One-NDS?

]]> http://blogs.kuppingercole.com/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/comment-page-1/#comment-38 Directory Thu, 05 Feb 2009 16:18:45 +0000 http://blogs.kuppingercole.de/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/#comment-38 Very informative article, which I found quite useful. Cheers ,Jay Very informative article, which I found quite useful. Cheers ,Jay

]]> http://blogs.kuppingercole.com/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/comment-page-1/#comment-119 sampo_kello4682 Tue, 22 Jan 2008 12:46:00 +0000 http://blogs.kuppingercole.de/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/#comment-119 Much of what Apertio does can be done with a virtual directory that supports multiple protocols. The HSS or GUP side requires Diameter, which is available on market place. The future of supporting end user applications will require a web service interface - potentially with identity management such as SAML or Liberty. This is also available today. I guess the next contender for telco directory solution just has to do a convincing integration. From what I've learned from telco projects is that "you do not touch HLR!" Apertio's main contribution was to convince telcos that this area can indeed be touched. Whoever is equally convincing, will rule the roost. Much of what Apertio does can be done with a virtual directory that supports multiple protocols. The HSS or GUP side requires Diameter, which is available on market place. The future of supporting end user applications will require a web service interface – potentially with identity management such as SAML or Liberty. This is also available today. I guess the next contender for telco directory solution just has to do a convincing integration. From what I've learned from telco projects is that "you do not touch HLR!" Apertio's main contribution was to convince telcos that this area can indeed be touched. Whoever is equally convincing, will rule the roost.

]]> http://blogs.kuppingercole.com/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/comment-page-1/#comment-15 Sampo Kellomäki Tue, 22 Jan 2008 11:46:00 +0000 http://blogs.kuppingercole.de/gaehtgens/2008/01/15/the-importance-of-apertios-acquisition-for-the-directory-world/#comment-15 Much of what Apertio does can be done with a virtual directory that supports multiple protocols. The HSS or GUP side requires Diameter, which is available on market place. The future of supporting end user applications will require a web service interface - potentially with identity management such as SAML or Liberty. This is also available today. I guess the next contender for telco directory solution just has to do a convincing integration. From what I've learned from telco projects is that "you do not touch HLR!" Apertio's main contribution was to convince telcos that this area can indeed be touched. Whoever is equally convincing, will rule the roost. Much of what Apertio does can be done with a virtual directory that supports multiple protocols. The HSS or GUP side requires Diameter, which is available on market place. The future of supporting end user applications will require a web service interface – potentially with identity management such as SAML or Liberty. This is also available today. I guess the next contender for telco directory solution just has to do a convincing integration. From what I’ve learned from telco projects is that “you do not touch HLR!” Apertio’s main contribution was to convince telcos that this area can indeed be touched. Whoever is equally convincing, will rule the roost.

]]>