informationcardjava Wiki & Documentation Rss Feed

Updated Wiki: Home

Jayfro — Tue, 28 Oct 2008 14:28:23 GMT

Summary

The purpose of this project is to demonstrate Information Card interoperability on heterogeneous platforms written using Java language to support Apache Tomcat, JBoss & SUN Application Server platforms running on Linux or Windows.

Windows CardSpace and InformationCard are SSO (Single-Sign-on) solutions from Microsoft. This project is called JInformationCard as it aims at developing a platform independent plugin for Java-based web application servers, which finally allows to use InformationCard functionality with an existing web application with minimum integration effort.

We have set up a demo site where you may start right away with testing JInformationCard functionality. Please provide feedback afterwards so we can improve it further.

JInformationCard is published under the BSD license.
JInformationCard is developed by the Fraunhofer Institute FOKUS in Germany.

Links

Project Homepage

News

SourceForge.net: SF.net Project News: Information Card Java News Feed

move to Subversion for source control

Tuesday, October 14, 2008 | From SourceForge.net: SF.net Project News: Information Card Java

going forward, we'll be using Subversion for source code access. While the old code will remain available from the CVS repository, all new development (well, more like a rewrite :) is now available through the subversion repo. (0 comments)

JInfocard 2.0

Tuesday, October 14, 2008 | From SourceForge.net: SF.net Project News: Information Card Java

Hey InfoCard optimists â€¦ (0 comments)

Relaunch of the Mini-Shop

Monday, August 20, 2007 | From SourceForge.net: SF.net Project News: Information Card Java

We have relaunched our test-page and sandbox. We hope it will demonstrate more effectively the InformationCard-functionalities. Have a look at: (0 comments)

Final steps ahead

Thursday, July 05, 2007 | From SourceForge.net: SF.net Project News: Information Card Java

After 2 and a half month we are almost finished with an acceptable version of the java web based platform.
The mini shop is demonstrating Information Card interoperability on heterogeneous platforms using Java language.
This is why we call the community to give us some final feedback on the current code, so that we are able to consider your feedback and improve the source code as soon as possible. (0 comments)

InformationCard Java launched

Monday, May 21, 2007 | From SourceForge.net: SF.net Project News: Information Card Java

You will find all relevant information regarding the project InformationCard Java at http://informationcard.sourceforge.net/ (0 comments)

SourceForge.net: SF.net Project News: Information Card Java News Feed

Updated Wiki: Home

Jayfro — Tue, 28 Oct 2008 10:57:24 GMT

Summary

Links

Project Homepage

News

JInformationCard - News Feed

Relaunch of the Mini-Shop

Tuesday, August 21, 2007 | From JInformationCard -

We have relaunched our test-page and sandbox. We hope it will demonstrate more effectively the InformationCard-functionalities.

Within the next week we hope to put the full documentation online, so that web admins and other users have the opportunity to install our java package.

We hope to meet your expectations, please do not hesitate to contact us.

Final steps ahead

Thursday, July 05, 2007 | From JInformationCard -

After 2 and a half month we are almost finished with an acceptable version of the java web based platform.
The bio mini shop is demonstrating Information Card interoperability on heterogeneous platforms using Java language.
This is why we call the community to give us some final feedback on the current code, so that we are able to consider your feedback and improve the source code as soon as possible.

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

More and more it has become common practice for all kinds of service providers to offer users online access via username and password. To ensure the security of our private data we have now uncountable usernames and passwords and sometimes we keep on guessing which username we used for this service and which password we used for that service. The alternative is to maintain a list of usernames and passwords. But where to keep this list?

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

JInformationCard - News Feed

UPDATED WIKI: Home

Jayfro — Thu, 20 Sep 2007 11:31:37 GMT

Summary

Links

Project Homepage

News

NEWS FEED

Relaunch of the Mini-Shop

Tuesday, August 21, 2007 | From JInformationCard -

We have relaunched our test-page and sandbox. We hope it will demonstrate more effectively the InformationCard-functionalities.

Within the next week we hope to put the full documentation online, so that web admins and other users have the opportunity to install our java package.

We hope to meet your expectations, please do not hesitate to contact us.

Final steps ahead

Thursday, July 05, 2007 | From JInformationCard -

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

skonman — Tue, 24 Jul 2007 11:04:17 GMT

Summary

The purpose of this project is to demonstrate Information Card interoperability on heterogeneous platforms written using Java language to support Apache Tomcat, JBoss & Websphere Application Server platforms running on Linux or Windows.

Windows CardSpace and InformationCard are SSO (Single-Sign-on) solutions from Microsoft. This project is called JInformationCard as it aims at developing a platform independent plugin for Java-based web application servers, which finally allows to use InformationCard functionality with an existing web application with minimum integration effort.

We have set up a demo site where you may start right away with testing JInformationCard functionality. Please provide feedback afterwards so we can improve it further.

JInformationCard is published under the BSD license.
JInformationCard is developed by the Fraunhofer Institute FOKUS in Germany.

Links

Project Homepage

News

NEWS FEED

Final steps ahead

Thursday, July 05, 2007 | From JInformationCard -

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

kazcor — Thu, 05 Jul 2007 10:27:06 GMT

Summary

The purpose of this project is to demonstrate Information Card interoperability on heterogeneous platforms written using Java language to support Apache Tomcat, Sun Java Web Servers & Websphere Application Server platforms running on Linux or Windows.

Windows CardSpace and InformationCard are SSO (Single-Sign-on) solutions from Microsoft. This project is called JInformationCard as it aims at developing a platform independent plugin for Java-based web application servers, which finally allows to use InformationCard functionality with an existing web application with minimum integration effort.

We have set up a demo site where you may start right away with testing JInformationCard functionality. Please provide feedback afterwards so we can improve it further.

JInformationCard is published under the BSD license.
JInformationCard is developed by the Fraunhofer Institute FOKUS in Germany.

Links

Project Homepage

News

NEWS FEED

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

kazcor — Thu, 05 Jul 2007 10:26:50 GMT

Summary

Links

Project Homepage

News

Error rendering macro: rss Invalid parameter: url: no rss channel could be found

UPDATED WIKI: Home

kazcor — Thu, 05 Jul 2007 10:26:27 GMT

Summary

Links

Project Homepage

News

NEWS FEED

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

kazcor — Tue, 22 May 2007 10:24:12 GMT

Summary

Links

Project Homepage

News

NEWS FEED

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

kazcor — Tue, 22 May 2007 10:12:39 GMT

Summary

Links

Project Homepage

News

NEWS FEED

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

kazcor — Tue, 22 May 2007 10:08:47 GMT

News

NEWS FEED

JInformationCard Official Site launched

Friday, May 18, 2007 | From JInformationCard -

JInformationCard published

Friday, May 18, 2007 | From JInformationCard -

The Fraunhofer Intitute FOKUS is proud to announce a first release of JInformationCard to the public!

NEWS FEED

UPDATED WIKI: Home

Jayfro — Sun, 20 May 2007 20:09:34 GMT

History

Microsoft published Cardspace (formerly InfoCard) in May 2005 as Single Sign-on (SSO) solution and therefore as successor and replacement to Passport. One of the main critics on Passport was the storage of user data on external servers. CardSpace (former InfoCard) overcomes those barriers by storing private data on the users side and optional uses trusted third parties for the actual storage of authentication data. The underlying architecture itself with all subjects is called “The Identity Metasystem”, first developed by Microsoft´s Identity Architect, Kim Cameron, and actually being more a shared vision on solving basic identity challenges than a Microsoft specific initiative.

What it is

Windows CardSpace (WCS) is a technology that provides a management of digital identities with interoperability, security and ease-of-use in mind. With CardSpace it is possible to use various online services with only one user account/card instead of dealing with multiple usernames/passwords (U/P), bringing the idea of cards as used in the real world (credit card/ID card) to the internet for better usability, and a more realistic and comfortable experience of internet services. The card itself holds only meta informations on how to actually access private user data from so called “identity providers” (IP). Identity Providers may be trusted third parties holding a Security Token Service (STS) or even the user itself, in case a self-issued card is used, which actually stores all private data on the local computer. CardSpace´s design goals include a seamless integration into existing browsers and web sites independent of the underlying platforms, as well as specific browser issues that affect the user experience directly, like graceful fall-back in case of missing WCS support or being possible to handle WCS with security settings set to a high level.

Architectural diagram

Open Standards

The Information Card model is built on open, interoperable communication standards that can been implemented on Windows and other platforms. The relying party can be implemented in Java on Apache TomCat or Sun Java System Web Server. For more information on interoperability, please visit Identity Selector Interoperability Profile.

How it works

When a user connects to a website with CardSpace support, an Identity Selector will open, providing all available cards that may be used for authentication. The user simply selects a card and depending on the cardtype (managed or self-issued) a security token is send back to the site from either a IP or the local computer. To let managed cards out of scope for now, here the general flow on what will happen for self-issued cards:

1. The user connects with a browser to a relying party (RP) holding a desired service

* selects a service and WCS login appears automatically, or
* performs a direct login query via WCS where usual U/P login exists

2. The RP sends back some claims that are required to be met

3. The browser pops up an Identity Selector presenting a list of cards providing those claims

4. The user selects a card

5. The Identity Selector connects to the IP/STS - in this case the client itself – and receives a security token

6. The security token is send back to the RP

7. The RP validates the token and grants access to the services

Project aims

JCardSpace is meant to be an implementation of CardSpace on the server side, focusing on open-source Java driven web containers. With JCardSpace it will be finally possible to simply enhance an already existing web application by adding CardSpace support. The project aims to develop an application module that can easily be integrated for the core functionality as well as providing the necessary documentation to include the functionality into the existing authentication mechanisms with a minimum effort.

Project milestones

M1:
One of the first steps necessary is to set up an communication platform where users and developers may publish and access documentation, discuss about project details and gain informations on the current state of the project. In this case this is be done by using SourceForge and CodePlex as portal, which already contain the needed functionality like document handling, mailing list, forums, wiki and management of source code and files. Once those sites are set up they need to be filled with usable information that are already available like informations on CardSpace itself, a summary of the project and a list of milestones to be reached in the near future. With those informations the community should get motivated to keep in touch during the development process. This milestone is reached when the project is made public and announced in the usual places.

M2:
The second milestone needs to be fulfilled in the first month and comprises the main development phase, where the implementation is actually developed and deployed on an exemplary web container. Once this first version of the final product is ready for testing, a sandbox needs to be set up and should be linked on the project page. This way the community is able to contribute to the testing phase and make suggestions for further enhancements and fixes.

M3:
During the second month the actual testing takes place. This is were input from the community is worked up, to finalize the software. After all main implementation tasks are done, the code needs to be reviewed and tested before finally the quality assurance takes place. According to the results gained in the assurance process, last modifications may be done, that will be tested, reviewed and need to pass the quality assurance gain.

M4:
The last month that is planned for this initial release so far is dedicated to the finalization of the product, which includes writing of documents that describe extensive development details, deployment steps and a detailed overview on the architecture, to allow third parties to extend the product easily. In that final milestone it is also needed to publish, how JCardSpace will evolve further, what functionality is planned and when the next release may be published.

Screenshot Sandbox Bio Mini Shop

Licensing

JCardSpace is Free Software and falls under the BSD license.

Summarized, according to this license JCardSpace may be redistributed in any way with or without modification in source or binary form under the condition that a copy of the license is included and that the name of the company (Fraunhofer) is not used for selling or promoting the product itself. Finally the license consists of the usual disclaimer about rejecting any warranties on the product and the possible consequences involved in modifying and/or using it.

Grab a copy of the full license text here.

Fraunhofer Big Picture

The Fraunhofer-Gesellschaft, the largest organization for applied research in Europe, sees itself as a service company, offering its various scientific and technological know how to private and public organisations and partners. The Fraunhofer-Gesellschaft is made up of 56 institutes staffed by a total of roughly 12,500 employees, with about 1 billion EUR research budget annually.

The Fraunhofer Institute for Open Communication Systems (FOKUS) is an institute of the Fraunhofer Gesellschaft and has developed for 15 years solutions for partners from industries, research and public administrations in areas such as integration of networks, technologies, adaption and management of services, applications as well as measuring and testing of diversified telecommunicationsystems.

The Fraunhofer FOKUS offers in form of their interoperability laboratory industry partners and public organisations a comprehensive technical infrastructure and all the expertise needed to evaluate interoperability of IT systems from different vendors on the organizational, semantic and technical level.

UPDATED WIKI: Home

Jayfro — Sun, 20 May 2007 19:59:11 GMT

History

Microsoft published Cardspace (formerly InfoCard) in May 2005 as Single Sign-on (SSO) solution and therefore as successor and replacement to Passport. One of the main critics on Passport was the storage of user data on external servers. CardSpace (former InfoCard) overcomes those barriers by storing private data on the users side and optional uses trusted third parties for the actual storage of authentication data. The underlying architecture itself with all subjects is called “The Identity Metasystem”, first developed by Microsoft´s Identity Architect, Kim Cameron, and actually being more a shared vision on solving basic identity challenges than a Microsoft specific initiative.

What it is

Windows CardSpace (WCS) is a technology that provides a management of digital identities with interoperability, security and ease-of-use in mind. With CardSpace it is possible to use various online services with only one user account/card instead of dealing with multiple usernames/passwords (U/P), bringing the idea of cards as used in the real world (credit card/ID card) to the internet for better usability, and a more realistic and comfortable experience of internet services. The card itself holds only meta informations on how to actually access private user data from so called “identity providers” (IP). Identity Providers may be trusted third parties holding a Security Token Service (STS) or even the user itself, in case a self-issued card is used, which actually stores all private data on the local computer. CardSpace´s design goals include a seamless integration into existing browsers and web sites independent of the underlying platforms, as well as specific browser issues that affect the user experience directly, like graceful fall-back in case of missing WCS support or being possible to handle WCS with security settings set to a high level.

Open Standards

The Information Card model is built on open, interoperable communication standards that can been implemented on Windows and other platforms. The relying party can be implemented in Java on Apache TomCat or Sun Java System Web Server. For more information on interoperability, please visit Identity Selector Interoperability Profile.

How it works

When a user connects to a website with CardSpace support, an Identity Selector will open, providing all available cards that may be used for authentication. The user simply selects a card and depending on the cardtype (managed or self-issued) a security token is send back to the site from either a IP or the local computer. To let managed cards out of scope for now, here the general flow on what will happen for self-issued cards:

1. The user connects with a browser to a relying party (RP) holding a desired service

* selects a service and WCS login appears automatically, or
* performs a direct login query via WCS where usual U/P login exists

2. The RP sends back some claims that are required to be met

3. The browser pops up an Identity Selector presenting a list of cards providing those claims

4. The user selects a card

5. The Identity Selector connects to the IP/STS - in this case the client itself – and receives a security token

6. The security token is send back to the RP

7. The RP validates the token and grants access to the services

Project aims

JCardSpace is meant to be an implementation of CardSpace on the server side, focusing on open-source Java driven web containers. With JCardSpace it will be finally possible to simply enhance an already existing web application by adding CardSpace support. The project aims to develop an application module that can easily be integrated for the core functionality as well as providing the necessary documentation to include the functionality into the existing authentication mechanisms with a minimum effort.

Project milestones

M1:
One of the first steps necessary is to set up an communication platform where users and developers may publish and access documentation, discuss about project details and gain informations on the current state of the project. In this case this is be done by using SourceForge and CodePlex as portal, which already contain the needed functionality like document handling, mailing list, forums, wiki and management of source code and files. Once those sites are set up they need to be filled with usable information that are already available like informations on CardSpace itself, a summary of the project and a list of milestones to be reached in the near future. With those informations the community should get motivated to keep in touch during the development process. This milestone is reached when the project is made public and announced in the usual places.

M2:
The second milestone needs to be fulfilled in the first month and comprises the main development phase, where the implementation is actually developed and deployed on an exemplary web container. Once this first version of the final product is ready for testing, a sandbox needs to be set up and should be linked on the project page. This way the community is able to contribute to the testing phase and make suggestions for further enhancements and fixes.

M3:
During the second month the actual testing takes place. This is were input from the community is worked up, to finalize the software. After all main implementation tasks are done, the code needs to be reviewed and tested before finally the quality assurance takes place. According to the results gained in the assurance process, last modifications may be done, that will be tested, reviewed and need to pass the quality assurance gain.

M4:
The last month that is planned for this initial release so far is dedicated to the finalization of the product, which includes writing of documents that describe extensive development details, deployment steps and a detailed overview on the architecture, to allow third parties to extend the product easily. In that final milestone it is also needed to publish, how JCardSpace will evolve further, what functionality is planned and when the next release may be published.

Licensing

JCardSpace is Free Software and falls under the BSD license.

Summarized, according to this license JCardSpace may be redistributed in any way with or without modification in source or binary form under the condition that a copy of the license is included and that the name of the company (Fraunhofer) is not used for selling or promoting the product itself. Finally the license consists of the usual disclaimer about rejecting any warranties on the product and the possible consequences involved in modifying and/or using it.

Grab a copy of the full license text here.

Fraunhofer Big Picture

The Fraunhofer-Gesellschaft, the largest organization for applied research in Europe, sees itself as a service company, offering its various scientific and technological know how to private and public organisations and partners. The Fraunhofer-Gesellschaft is made up of 56 institutes staffed by a total of roughly 12,500 employees, with about 1 billion EUR research budget annually.

The Fraunhofer Institute for Open Communication Systems (FOKUS) is an institute of the Fraunhofer Gesellschaft and has developed for 15 years solutions for partners from industries, research and public administrations in areas such as integration of networks, technologies, adaption and management of services, applications as well as measuring and testing of diversified telecommunicationsystems.

The Fraunhofer FOKUS offers in form of their interoperability laboratory industry partners and public organisations a comprehensive technical infrastructure and all the expertise needed to evaluate interoperability of IT systems from different vendors on the organizational, semantic and technical level.

UPDATED WIKI: Home

Jayfro — Sun, 20 May 2007 19:58:20 GMT

History

Microsoft published Cardspace (formerly InfoCard) in May 2005 as Single Sign-on (SSO) solution and therefore as successor and replacement to Passport. One of the main critics on Passport was the storage of user data on external servers. CardSpace (former InfoCard) overcomes those barriers by storing private data on the users side and optional uses trusted third parties for the actual storage of authentication data. The underlying architecture itself with all subjects is called “The Identity Metasystem”, first developed by Microsoft´s Identity Architect, Kim Cameron, and actually being more a shared vision on solving basic identity challenges than a Microsoft specific initiative.

What it is

Windows CardSpace (WCS) is a technology that provides a management of digital identities with interoperability, security and ease-of-use in mind. With CardSpace it is possible to use various online services with only one user account/card instead of dealing with multiple usernames/passwords (U/P), bringing the idea of cards as used in the real world (credit card/ID card) to the internet for better usability, and a more realistic and comfortable experience of internet services. The card itself holds only meta informations on how to actually access private user data from so called “identity providers” (IP). Identity Providers may be trusted third parties holding a Security Token Service (STS) or even the user itself, in case a self-issued card is used, which actually stores all private data on the local computer. CardSpace´s design goals include a seamless integration into existing browsers and web sites independent of the underlying platforms, as well as specific browser issues that affect the user experience directly, like graceful fall-back in case of missing WCS support or being possible to handle WCS with security settings set to a high level.

Open Standards

The Information Card model is built on open, interoperable communication standards that can been implemented on Windows and other platforms. The relying party can be implemented in Java on Apache TomCat or Sun Java System Web Server. For more information on interoperability, please visit Identity Selector Interoperability Profile.

How it works

When a user connects to a website with CardSpace support, an Identity Selector will open, providing all available cards that may be used for authentication. The user simply selects a card and depending on the cardtype (managed or self-issued) a security token is send back to the site from either a IP or the local computer. To let managed cards out of scope for now, here the general flow on what will happen for self-issued cards:

1. The user connects with a browser to a relying party (RP) holding a desired service

* selects a service and WCS login appears automatically, or
* performs a direct login query via WCS where usual U/P login exists

2. The RP sends back some claims that are required to be met

3. The browser pops up an Identity Selector presenting a list of cards providing those claims

4. The user selects a card

5. The Identity Selector connects to the IP/STS - in this case the client itself – and receives a security token

6. The security token is send back to the RP

7. The RP validates the token and grants access to the services

Project aims

JCardSpace is meant to be an implementation of CardSpace on the server side, focusing on open-source Java driven web containers. With JCardSpace it will be finally possible to simply enhance an already existing web application by adding CardSpace support. The project aims to develop an application module that can easily be integrated
for the core functionality as well as providing the necessary documentation to include the functionality into the existing authentication mechanisms with a minimum effort.

Project milestones

M1:
One of the first steps necessary is to set up an communication platform where users and developers may publish and access documentation, discuss about project details and gain informations on the current state of the project. In this case this is be done by using SourceForge and CodePlex as portal, which already contain the needed functionality like document handling, mailing list, forums, wiki and management of source code and files. Once those sites are set up they need to be filled with usable information that are already available like informations on CardSpace itself, a summary of the project and a list of milestones to be reached in the near future. With those informations the community should get motivated to keep in touch during the development process. This milestone is reached when the project is made public and announced in the usual places.

M2:
The second milestone needs to be fulfilled in the first month and comprises the main development phase, where the implementation is actually developed and deployed on an exemplary web container. Once this first version of the final product is ready for testing, a sandbox needs to be set up and should be linked on the project page. This way the community is able to contribute to the testing phase and make suggestions for further enhancements and fixes.

M3:
During the second month the actual testing takes place. This is were input from the community is worked up, to finalize the software. After all main implementation tasks are done, the code needs to be reviewed and tested before finally the quality assurance takes place. According to the results gained in the assurance process, last modifications may be done, that will be tested, reviewed and need to pass the quality assurance gain.

M4:
The last month that is planned for this initial release so far is dedicated to the finalization of the product, which includes writing of documents that describe extensive development details, deployment steps and a detailed overview on the architecture, to allow third parties to extend the product easily. In that final milestone it is also needed to publish, how JCardSpace will evolve further, what functionality is planned and when the next release may be published.

Licensing

JCardSpace is Free Software and falls under the BSD license.

Summarized, according to this license JCardSpace may be redistributed in any way with or without modification in source or binary form under the condition that a copy of the license is included and that the name of the company (Fraunhofer) is not used for selling or promoting the product itself. Finally the license consists of the usual disclaimer about rejecting any warranties on the product and the possible consequences involved in modifying and/or using it.

Grab a copy of the full license text here.

Fraunhofer Big Picture

The Fraunhofer-Gesellschaft, the largest organization for applied research in Europe, sees itself as a service company, offering its various scientific and technological know how to private and public organisations and partners. The Fraunhofer-Gesellschaft is made up of 56 institutes staffed by a total of roughly 12,500 employees, with about 1 billion EUR research budget annually.

The Fraunhofer Institute for Open Communication Systems (FOKUS) is an institute of the Fraunhofer Gesellschaft and has developed for 15 years solutions for partners from industries, research and public administrations in areas such as integration of networks, technologies, adaption and management of services, applications as well as measuring and testing of diversified telecommunicationsystems.

The Fraunhofer FOKUS offers in form of their interoperability laboratory industry partners and public organisations a comprehensive technical infrastructure and all the expertise needed to evaluate interoperability of IT systems from different vendors on the organizational, semantic and technical level.