Our first implementation of Single Sign-On used JumpCloud as Identity Provider. Because of that, our documentation primarily points towards JC and AWS guides on how to implement the integration with AWS SSO.
We have now dropped the JumpCloud integration in favor of AWS's own solution.
The documentation should reflect the current approach to Single Sign-On authentication, which is using AWS SSO by default.
Having already researched and implemented the use of JC as an external identity provider, it seems reasonable to keep this knowledge documented as an alternative.
Our first implementation of Single Sign-On used JumpCloud as Identity Provider. Because of that, our documentation primarily points towards JC and AWS guides on how to implement the integration with AWS SSO. We have now dropped the JumpCloud integration in favor of AWS's own solution.
The documentation should reflect the current approach to Single Sign-On authentication, which is using AWS SSO by default.
Having already researched and implemented the use of JC as an external identity provider, it seems reasonable to keep this knowledge documented as an alternative.