That depends on whether you are running embedded or external. If external,
you should be changes to tomcat yourself and manually and you should review
the tomcat documentation. If embedded, then you should consider using
`server.ssl.enabled-protocols=` which is a setting provided by Spring Boot
Hello, with the exact same issue, we try with versions 6.2.6 / 6.2.7 /
6.3.1 but still the same problem. Did you solved it and how ? thank you
Le jeudi 9 juillet 2020 à 19:50:25 UTC+2, emreer...@gmail.com a écrit :
> Thank you Ray for your quick response.
>
> - When I start with
On Monday, February 1, 2021 at 9:06:50 PM UTC+4 thorste...@gmail.com wrote:
> Can you guys tell me, if it is possible to set this option and how?
>
Hello, if by possible you mean out of the box, then no and not yet.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom:
Could you share an example for one that does cause headaches?
On Wednesday, February 3, 2021 at 2:24:41 AM UTC+4 Keith Alston (Staff)
wrote:
> I've got services I want to convert from ADFS to CAS. Many are simple but
> a few give me nothing but headaches.
> Anyone have a methodology(or tool)
Mahalo nui loa! The UnboundID workaround appears to solve the problem so I
don't need to further pursue trying to substitute a newer version of the
Ldaptive library. I wasn't able to find any documentation on the
UnboundIDProvider though (what does it do specifically, and where would I
have found
We've been disabling TLS protocols and ciphers that have been deemed weak
(e.g., TLSv1, TLSv1.1). While we've done so for our Tomcat configs, I
noticed the following in our CAS logs today:
DEBUG [org.apereo.cas.authentication.FileTrustStoreSslSocketFactory] -
DEBUG
Hello all,
We are currently using memcached to store store tickets using the following
configuration
```
cas.ticket.registry.memcached.servers=localhost:11213
cas.ticket.registry.memcached.transcoder=KRYO
```
After a recent upgrade from cas 6.2.7 -> 6.3.1 i noticed that, after cas is
