Idea Details

An Enhancement Request : Aggregation of authentication scheme using CookieProvider in multiple doma

Last activity 06-04-2019 11:47 AM
Anon Anon's profile image
03-28-2016 01:38 AM

Our client will use the CASSO in the configuration of multiple domains, but they wishes to use one authentication scheme in all WebAgent on multiple domains.

 

We believe that can be realized by operating the WebAgent of the authentication server as CookieProvider.

 

However, your support answer's following.
So it can not be implemented in our client.

 

<Answer>
Authentication server and WebAgent Even with CookieProvider must be the same domain.

 

Client is considering a transfer to CASSO from other products.

There is this matter as one of the study material.
Of course, they are serious about this matter of support propriety.

 

<Product Environment>
Therefore we would like to support the following Environment.

  CA Single Sign-On r12.51 (Containing SP Level)
  CA Single Sign-On r12.52 (Containing SP Level)

 

<Business Impact>
If this enhancement is not approved, we may lose a customer.
This is a big customer (expanded to 3,600,000 users) and this environment is necessary.

So this enhancement have big influence for business.

 

Would you mind supporting this matter?


Comments

05-25-2017 03: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 suggested enhancement. Based on current roadmap priorities and/or the limited amount of community support for this idea over the last year (please see this document describing how we are reviewing ideas: https://communities.ca.com/docs/DOC-231170123), we are not accepting this idea into the product backlog. Therefore, it is being moved to a “Not Planned” status.

04-04-2016 02:42 PM

Hello!

 

Can you explain a bit more about the use case that is being requested? I don't quite understand how you would want to use an authentication server for multiple domains. An example of the URLs and the flow would be very helpful.

 

thanks,

 

Rob