Response from Misagh Moayyed: "The private key is auto-generated when path is defined. You don't need to get one from Okta. That's not how #SAML <https://twitter.com/hashtag/SAML?src=hash> works. The signing certificate from Okta is in their metadata file. The keystore contains your private/public keys as a SAML SP."
On Monday, October 2, 2017 at 10:19:48 AM UTC+3, Антон Шихмат wrote: > > Hello everyone, > > I'm trying to integrate CAS SAML 2 delegated auth with OKTA using this > tutorial https://apereo.github.io/2017/03/22/cas51-delauthn-tutorial/ > CAS properties file should contain such values: keystore path (that > contains OKTA signing certificate), keystore password and private key > password. > OKTA provides signing certificate, so I can create a keystore using it. > But OKTA does not provide private key for this certificate (or at least I > cannot find it). I cannot left this value empty, because I will receive an > exception during CAS startup. > Can anyone help me, how can I configure OKTA integration without private > key or where I can find it? > > Thanks > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e0f20259-2b41-4e08-af2c-afbcf1dde46f%40apereo.org.
