Details
-
Story
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
7.3.x
-
Committed
-
Iteration 43, Iteration 44, Iteration 45, Iteration 46, Iteration 47, Iteration 48, Iteration 49
-
Manual
Description
Description
We need a way to send SAML configuration data from one portal instance in SaaS into another portal instance in SaaS.
A use case for example is the following: a client configures SAML in its Sandbox Environment, checks that it works correctly and wants to send it to its Production Environment to start using it in the same way.
Acceptance Criteria
- As a Portal-Wide Administrator, I want to send and apply all the necessary SAML configuration of a given portal instance to the appropriate instance so that the SAML works immediately if the key store is at the given path.
Attachments
Issue Links
- depends on
-
LPS-120375 SAML SP configuration export doesn't transmits the IDPConnection's metadata url
- Closed
- is related to
-
LPS-114916 Get to know how the data migration is happening when a customer goes from former version to SaaS environment
-
- Closed
-
- relates
-
LRDOCS-9354 User Document for SAML enhancements
-
- Closed
-
- Wiki Page
-
Wiki Page Loading...