CAS module ticket length format

[Loïc Naud]

Hi,

Acutally I'm installing IDP 5.1.3 with CAS Module, I want to reduce the 
length of tickets generated by the CAS module because my CAS clients 
can't handle and i can't modify my CAS clients

according to this thread 
http://shibboleth.net/pipermail/users/2017-April/035522.html I just need 
to add the following block <alias name="simpleTicketService" 
alias="shibboleth.CASTicketService" />
But the lentgh of the ticket is the same
ex: 
ST-AADXGZLDOJSXIMNUHZK6EISNVWHTPLARDGLLYA6W2PQCTUMTVTWOOMNCP6XVIVH33CLNXUTMJMY6TWXAO35LRQN2XXSQSRJECE33T5RY3PTGPZ45DSMWQCNA4SGUQCBL45YZ63CKKDYKCXZQGGYETTJMZ3HSYBFOSXDN3NBY7QA6G22TZBBQMH2RUJAXS3HBG7ZTNNPYQOMLYIAVQ2DWE2EKATQ6HDEU3XN2C7EF2J7K5WSVST7OVNCIGTJ5EOVQLYKEU6MEDTSYIDJJ7GAFAQMVKSMTI7MYHQE4J32T6BKJW2WABAKOCN57ZBPUDD4WAFBZ2N5S7IWQYSFT5QQ5A3IOZE77C7TJT37EQ7N6FWPU635JQ4CEO3UYURMIKZ4YSZTIJ4Y6KEKIOJIASYMHGHGSXUELEZ4B42YZIYPG2RZYGIR4JJBCRLC7UG5A----

here are the contents of my cas-protocol.xml file:


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:c="http://www.springframework.org/schema/c"
        xmlns:p="http://www.springframework.org/schema/p"
        xmlns:util="http://www.springframework.org/schema/util"
        xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/context 
http://www.springframework.org/schema/context/spring-context.xsd
http://www.springframework.org/schema/util 
http://www.springframework.org/schema/util/spring-util.xsd"
        default-init-method="initialize"
        default-destroy-method="destroy">

     <!--
        | The CAS service registry defines verified relying parties by 
endpoint URI.
        | The default implementation treats the ID of each entry as a 
regular expression defining a logical group of
        | services whose URIs match the expression.
        |
        | This bean is reloaded periodically according to 
%{idp.home}/conf/services.properties.
        -->

     <bean id="reloadableServiceRegistry"
class="%{idp.cas.serviceRegistryClass:net.shibboleth.idp.cas.service.PatternServiceRegistry}">
         <property name="definitions">
             <list>
                <bean 
class="net.shibboleth.idp.cas.service.ServiceDefinition"
                      c:regex="^https://xx\.xx.xx/.*"
                      p:group="non-proxying-services"
                      p:authorizedToProxy="true"/>
                <bean 
class="net.shibboleth.idp.cas.service.ServiceDefinition"
                      c:regex="https://xx.xx.xx/xx/.*"
                      p:group="non-proxying-services"
                      p:authorizedToProxy="true"/>
             </list>
         </property>
     </bean>

     <!-- Alias definition -->
     <alias name="simpleTicketService" 
alias="shibboleth.CASTicketService" />

     <!--
        | The predicate used to determine whether IdP session validation 
is performed during the process of granting
        | a proxy ticket. When the predicate evaluates to true, an IdP 
session is resolved and validated prior to
        | granting a proxy ticket. This feature prevents issuing proxy 
tickets when an IdP session is expired, but comes
        | at the cost of requiring server-side storage of IdP session 
data. If this is configured to a predicate that
        | evaluates to true under any condition, a server-side storage 
service must be enabled for IdP session
        | storage. The most common non-default value is "alwaysTrue."
        -->
     <bean id="shibboleth.CASProxyValidateIdPSessionPredicate" 
parent="shibboleth.Conditions.FALSE" />

     <!--
        | Define the list of static certificates that you trust to 
secure CAS proxy callback endpoints.
        | Typically these are CA certificates and apply to _all_ CAS 
proxy callback endpoints.
        | This facility complements the capability to supply 
relying-party-specific certificates in SAML metadata,
        | which is the preferred mechanism to specify CAS proxy trust 
material. In the case of metadata, self-signed
        | certificates are recommended.
        -->
     <util:list id="shibboleth.CASProxyTrustedCertificates" 
value-type="java.lang.String">
<!--<value>%{idp.home}/credentials/your_ca.pem</value>-->
     </util:list>

</beans>

How can I troubleshoot this issue ?

Thanks,
Loïc

-- 

*Logo UTLoïc NAUD | **Ingénieur Systèmes*
/SNUT > Infrastructure et support/
*Université de Toulouse*
Maison de la Recherche et de la Valorisation - MRV
118 route de Narbonne - 31062 Toulouse Cedex 09
Tél. : 05 62 25 01 28 <tel:05 62 25 01 28> / 06 26 62 98 50 <tel:06 26 
62 98 50> poste int. : 11 01 28

Facebook 
<http://www.facebook.com/pages/Universit%C3%A9-de-Toulouse/189718587732582> | 
X <https://x.com/Univ_Toulouse> | www.univ-toulouse.fr 
<http://www.univ-toulouse.fr/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20241121/304b0516/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C4ioN0Dm0jyQ4JYB.gif
Type: image/gif
Size: 43 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20241121/304b0516/attachment.gif>