We should investigate utilizing the Alfresco Identity Service for SSO vs. the our current approach. Doing so could simplify our SSO deployments and integrations with other products in the Alfresco suite.
We will also need to address non-Alfresco customers. I'm guessing it would be easiest to "fall back" to the existing SSO approach to support these customers as well as maintain backwards compatibility for existing Alfresco customers.
Note, this comes from a MNT request (https://alfresco.atlassian.net/browse/MNT-22503) that asks for us to support Alfresco IDS for AEV's ADF components, but if we're going to go down this route, it'd be better as something that's at the OpenContent layer.
We should investigate utilizing the Alfresco Identity Service for SSO vs. the our current approach. Doing so could simplify our SSO deployments and integrations with other products in the Alfresco suite.
We will also need to address non-Alfresco customers. I'm guessing it would be easiest to "fall back" to the existing SSO approach to support these customers as well as maintain backwards compatibility for existing Alfresco customers.
Note, this comes from a MNT request (https://alfresco.atlassian.net/browse/MNT-22503) that asks for us to support Alfresco IDS for AEV's ADF components, but if we're going to go down this route, it'd be better as something that's at the OpenContent layer.