Hello everyone, I am working on OKTA Logout and facing some issues while implementing it.
I have added signout parameters in OKTA account as below: Single Logout URL: https://localhost:8443/cas/logout SP issuer: urn:herb:saml:pac4j.org and also got Signature Certificate from OKTA and added it. but still, OKTA account is not properly logged out from the application. Do we need to add the service registry for Logout so that CAS will be able to connect with OKTA for logout? Is there anything missing from my side? Thanks, Sarika D. On Monday, 2 October 2017 12:49:48 UTC+5:30, Антон Шихмат 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/e44064f5-6069-4b99-82d3-f1b9248625be%40apereo.org.
