How to configure OpenText Documentum as SP with mujina idp to test SSO

[devendar-12]

Hi Harsta,

Thanks for your response on issue 59. In extension to this, i have few more questions, could you please help us.

If i use my CMS(OpenText Documentum) application as SP, what all attributes i need to configure in my web application which is hosted on linux machine, deployed on tomcat. We are working on SP initiated SSO.

1)How do i configure the application.yml file of the sp? and where ?
2)Where should i keep my metadata.xml file in my SP? ( in mujina as, the path for it is at mujina-sp\src\main\resources\saml..)
3)Where should i keep my certficate and private keys at SP's end?
4)Could you please help us with how the re-direction will happen from a CMS application ( SP) to the mujina-idp ?
5)Also, could you please let us know if any additional steps/parameters to be considered to have a SSO Test complete using Mujina as IDP and CMS application as SP.
6) I could see the "metadata.xml" in sp for the assertion sent, but once the user logged in the idp, from which configuration, it will be sent to the SP? Do we need to configure acs_url on this metadata or on the runtime property file at the SP file?
I am missing the flow from which file, the response would be sent from idp to SP once successfully logged in to the idp.

Please note that, we are using this in Dev environment only, we wanted to prove that using Mujina SSO is getting implemented for Documentum application.

Thanks

[oharsta]

I can answer questions about Mujina SP / IdP, but I can't answer questions on how to add SAML SP functionality to an arbitrary CMS. You'll have to ask those questions on the specific CMS issue tracker.

4. The SSO location of the Mujina IdP is https:<domain_name>/SingleSignOnService.
5. The ACS location of the SP is read by the IdP from the SAML authentication request send by the SP. As stated before, I have no knowledge on how your CMS SP is constructing / sending this SAML request.