Idea Details

CA SSO able to dynamically update SAML entries from metadata distributed on a URL

Last activity 12-17-2016 09:13 AM
Per w4VHUkVO's profile image
06-16-2015 02:49 AM

We have a lot of SAML federation where the federation presents the metadata from all involved partners in one single URL.

We also see that nearly every partnership we configure is using a URL for holding the metadata.

This URL is meant to be dynamically updated and all partners should update their configuration simultaneously.

 

This solution is not able to setup with CA SSO.

 

I want CA SSO to be able to dynamically read metadata from URL and update the corresponding partnerships when it is needed.

 

I also want CA SSO to be able to distribute the metadata in an URL, so that other partners could update their configuration according to this.


Comments

09-07-2016 05:45 PM

Thank you for your contribution of an enhancement idea to the CA Community. CA is continually working to improve its software and services to best meet the needs of its customers. Your input is vital to that effort. The CA Single Sign-On Product Management team has reviewed your suggested enhancement. Based on current roadmap priorities and/or the limited amount of community support for this idea, we are not accepting this idea into the product backlog. Therefore, it is being moved to a “Not Planned” status.

01-18-2016 04:25 AM

Thank you for your contribution of an enhancement idea to the CA Community. CA is continually working to improve its software and services to best meet the needs of its customers. Your input is vital to that effort. The CA Single Sign-On Product Management team has reviewed your enhancement suggestion and decided to maintain the idea for possible consideration in a future release. The Community will continue to be able to vote on this enhancement idea.

11-02-2015 03:16 PM

This is a MUST requirement in eGov 2.0:

kantara-report-egov-saml2-profile-2.0.pdf

 

192 Implementations MUST support the following mechanisms for the importation of

193 metadata:

194 local file

195 remote resource at fixed location accessible via HTTP 1.1 [RFC2616] or HTTP

196 1.1 over TLS/SSL [RFC2818]