[cas-user] Re: "FileNotFoundException" while Verifying Ticket. I don't get it!

Hello, if i remember me correctly, this was an problem with mime type. you need to override CASFilter.getTicketValidator() and add following extended url connection factory // we need own connection factory enriching the connection by Accept: application/xml header HttpURLConnectionFactory

Re: [cas-user] Avoid default services recreation cas overlay

Hello, you need your own configurations, which were not found. Try to find the right parameters for 5.1.4 eg (works in 5.2.0-x): cas.serviceRegistry.json.location: file:///etc/cas/services We also had other minor problems with 5.1.x and switched directly to 5.2.0-rc2. Regards, Gena

Re: [cas-user] No Signing or Encryption Key

Hello Bob, if you on 5.2.0 try the pattern below. I think, the messages ares misleading and should be improved. cas.tgc.crypto.encryption.key cas.tgc.crypto.signing.key Von meinem iPhone gesendet > Am 17.08.2017 um 23:16 schrieb Bob Dill : > > Hi All, > > I've been

Re: [cas-user] Re: No Signing or Encryption Key

Nice to hear, but with cas 5.2.x they were also renamed: cas.webflow.crypto.signing.key cas.webflow.crypto.encryption.ke Von meinem iPhone gesendet > Am 18.08.2017 um 00:25 schrieb Bob Dill : > > N -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list

[cas-user] Re: call to /proxy endpoint ends up in Error 404 although PT successfully created

I'm wondering, how other users retrieve proxy tickets in light of the described issue? Is this a right way to use org.jasig.cas.client:cas-client-core as Java client at all? On Wednesday, July 12, 2017 at 4:31:01 PM UTC+2, Gena Batalski wrote: > > Hello > > I'm getting the p

[cas-user] Re: call to /proxy endpoint ends up in Error 404 although PT successfully created

, July 12, 2017 at 4:31:01 PM UTC+2, Gena Batalski wrote: > > Hello > > I'm getting the problem while retrieving the proxy ticket. After the PT > successfully created and written to Audit-Log, the response processing > doesn't pick up the "protocol/2.0/casProxySucc

[cas-user] Re: call to /proxy endpoint ends up in Error 404 although PT successfully created

is to add the accept header to the proxy ticket validator and to proxy retriever. If the Cas30ProxyTicketValidator still be the official way to connect to CAS, i could propose the pull request. On Wednesday, July 12, 2017 at 4:31:01 PM UTC+2, Gena Batalski wrote: > > Hello > >

[cas-user] Re: call to /proxy endpoint ends up in Error 404 although PT successfully created

17 at 4:31:01 PM UTC+2, Gena Batalski wrote: > > Hello > > I'm getting the problem while retrieving the proxy ticket. After the PT > successfully created and written to Audit-Log, the response processing > doesn't pick up the "protocol/2.0/casProxySuccessView.html" t

[cas-user] call to /proxy endpoint ends up in Error 404 although PT successfully created

Hello I'm getting the problem while retrieving the proxy ticket. After the PT successfully created and written to Audit-Log, the response processing doesn't pick up the "protocol/2.0/casProxySuccessView.html" to render the ticket back but end up with Error 404. What is wrong? Regards, Gena

[cas-user] No flow mapping found for request with URI '/cas/cas2ProxySuccessView'

Hello, i'm facing the problem described in the subject while trying to retrieve a proxy ticket via endpoint /proxy . Am i missing some dependencies? The used version of CAS is 5.2.0-RC2 Overlay config: compile "org.apereo.cas:cas-server-webapp-tomcat:${project.'cas.version'}@war" // Enable

[cas-user] Proposal for OIDC Delegation Azure AD

Hello Community, i've already described the problem in short here , i would propose the modification. Because i'm newbie in CAS usage and development i need an expertise about this proposal. *What is done now* 1. Running CAS 5.1.0 Server

Re: [cas-user] OIDC Delegation

Hello, it seems that at least Azure doesn't accept additonal query parameters anymore: the *client_name* ist just removed from the redirect url. I've found an article here explaining the problem. So i think, the