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 3 Current »

Organizing page for material connected to the project to redesign the Service Provider software.

Why are we doing this? The original discussion is at SP4Details.

What are we doing? Rewriting the existing SP software to migrate the functions currently performed by the shibd process in C++ into Java, reusing the bulk of the code in OpenSAML and currently in the IdP, filling in gaps where necessary. Most of the current C++ code will be eliminated, and the agents for specific web servers will be stripped down as much as practical. New agents may be developed but this is not an initial goal.

When are we doing this? Work has started in 2022 in earnest and is likely to take most of 2023, if not longer.

Topics

  • DesignNotes

    • Brain dump of issues with the current code and brainstorming some of the problem space

  • Remoting Protocol

    • Draft material on the proposed remoting protocol and conventions for communication with the Java-based service/hub

  • Source Code

    • The new Java “service” that will replacing the existing dependencies is in the java-sp-server.git repository with the unwieldy placeholder name of Shibboleth SP Service.

    • The existing cpp-sp.git repository will continue to exist and work will be done on a branch for now, though eventually we’ll branch 3.x and merge that work up to main.

  • No labels