About EOS and EOL for SAML SSO Applications

Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials. See a list of our pre-built SAML applications. 

When an application stops supporting SAML or is sunsetted by the service provider, JumpCloud puts the application into an end of support (EOS) or an end of life (EOL) state. Read this article to find out what you can expect from JumpCloud when an application reaches EOS or EOL and which connectors are EOS or EOL. 

End of Support (EOS)

You can plan on the following when an application reaches EOS: 

• JumpCloud no longer supports updates for the connector.
• Your users maintain access to it. 
• If a connector becomes EOS after you configured it, the status in the Application list view changes from a green check mark to a yellow exclamation mark. The status in the Application Details panel also changes from green to yellow. 
• The connector is hidden from the Configure New SSO Application list, so you can’t configure a new instance of it. 

End of Life (EOL)

You can expect the following when an application reaches EOL:

• Our team contacts you if you’re using the connector, and they notify you about the EOL date. 
• JumpCloud no longer supports updates for the connector. 
• Your users don’t have access to it. 
• If a connector becomes EOL after you configured it, the status in the Application list view changes from a green check mark to a red exclamation mark. The status in the Application Details panel also changes from green to red. 
• The connector is hidden from the Configure New SSO Application list, so you can’t configure a new instance of it. 

When an application is given an EOS or EOL status, you can configure a replacement connector and communicate the change to your users.

See the below table of applications that have reached EOL or EOS at JumpCloud and recommended alternatives: