Integration-of-new-applications

eIAM Customer Change Plan / CC Plan

Background

The eIAM Customer Change Plan defines the time windows for deploying customer applications in the respective eIAM stages (REFERENCE, ACCEPTANCE, and PRODUCTION).

Thanks to the continuous development of the eIAM CI/CD (Continuous Integration/Continuous Deployment) platform and the completion of the migration to the FOITT RHOS container platform, new opportunities for customer changes are now available. The new architecture setup of the eIAM service enables uninterrupted deployment, providing greater flexibility in rolling out customer changes across all stages.

This flexibility benefits both you as the customer and us as your integration partner. Through coordination between eIAM Release Management and FOITT Change Management, it has been established that applications directly connected to the BTB (Federal Trust Broker) no longer need to submit change requests.

The following new rules now apply to customer changes, depending on the integration pattern and stage:

STS connection (directly to BTB)

Applications that are integrated as STS connections are connected directly to BTB in the new architecture without PEP. This allows them to maximise their benefit from the new possibilities. These applications have full flexibility and can roll out configuration changes at any time in coordination with their eIAM integrator (SIE) from REFERENCE to PRODUCTION.

STS-PEP Connection (No longer available for new integrations)

For applications still connected via a dedicated STS-PEP, we recommend contacting the eIAM integration team to plan an upgrade to the direct STS connection to BTB without PEP. This streamlined integration pattern, tailored to the new eIAM architecture, offers greater flexibility and additional benefits in terms of availability in disaster scenarios.

We would be happy to discuss the details with you in a meeting. Please plan the upgrade promptly to benefit from the enhanced support available for the "Early Majority."

RP-PEP Connection

For applications still connected via a dedicated RP-PEP, we recommend reviewing the Protection levels of your application and determining whether an RP-PEP connection is still necessary. Let eIAM advise you and, if possible, migrate to an STS connection directly to BTB without PEP.

For applications connected via RP-PEP, full flexibility is only available in the REFERENCE and ACCEPTANCE stages. Configuration changes can be made at any time in this stages.

In PRODUCTION, configuration changes for RP-PEP integrations can generally be made every Wednesday during the maintenance window from 6:00 PM onwards. Overarching freezes must, of course, be considered.


If you have any questions or concerns regarding eIAM integrations, changes, or operational eIAM aspects, please contact the following departments or individuals:

eIAM contact points
×