Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

About this page

This page contains pseudo component diagrams of Perun AAI general system architecture. The goal of this page is to provider the reader with basic understanding of what Perun AAI components are, what they do and how they are connected, as well as how they evolve over time.

  • Page owner: Peter Lényi

  • Classification: public

  • Target audience: Perun team, Perun AAI community and partners

Table of contents

Individual Perun AAI instances typically diverge from the general system architecture described below due to specific requirements. Furthermore, some Perun AAI instances might be in transition between different system architectures.

Perun AAI ~2023

Perun AAI general system architecture ca. fall of 2023.

Perun AAI - Overview (component diagram) - 2023

Perun AAI ~2024

Perun AAI general system architecture ca. 2024. Since the previous version, Perun ProxyIdP moves away from custom solutions and forked technologies to actively maintained third party solutions with minimum customisations like SATOSA by GÉANT; Perun IdM moves away from the old GWT-based GUI framework to a new one made with Angular and deprecates components with little-to-no use; and our custom SPReg application is replaced with Federation Registry application by EGI.

Perun AAI - Overview (component diagram) - 2024

  • No labels

Support: perun@cesnet.cz