Assuming you mean for CAS to be your IdP...

When you start CAS for the first time with the SAML IdP enabled, it will
generate keys and store them in /etc/cas/saml for you. You need to copy
them from there back to a safe location so that they get re-deployed
whenever you update the server.

See, for example, here:
https://dacurry-tns.github.io/deploying-apereo-cas/building_server_saml_install-and-test-the-idp.html

--Dave


--

DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY

71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • [email protected]

[image: The New School]

On Thu, May 10, 2018 at 2:05 PM, John D Giotta <[email protected]> wrote:

> For a IdP metadata file, what should the KeyDescriptor be? Is it the
> public key of the web server?
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit https://groups.google.com/a/
> apereo.org/d/msgid/cas-user/a66f9075-e1ba-4181-9f29-
> d3f4c185b654%40apereo.org
> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/a66f9075-e1ba-4181-9f29-d3f4c185b654%40apereo.org?utm_medium=email&utm_source=footer>
> .
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CA%2Bd9XAMKQLrUT93-zTG6gy%2BTtzuv695Q7YBcGFrrumhu0Ne8NA%40mail.gmail.com.

Reply via email to