nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Tomcat sessions and Alfresco tickets, is it the same ?

zomurn

Hello,

I would say no because I have a problem with that :

I'd like to prevent two connections of the same user in alfresco.
For this, in the login() method I check all tickets with :

Set<String> lTickets = authenticationServiceImpl.getUsersWithTickets( true );‍

If the user who attempt to login has the login present in the "lTickets" returned set. I refuse to log the person in alfresco.
This works.
The problem arrives when the end user (very end) close the windows directly.
Then the unique way to kill the session is with tomcat parameter in web.xml "session-timeout".
But waiting the session to be killed thanks tomcat so that the user can connect again doesn't always work but sometimes.
So can you help me to kill the user session (or check to double login) when the user close navigator (without clicking logout).

Thanks

Find more posts tagged with

Comments

zomurn

I saw the method public void setOneOff(boolean oneOff) in InMemoryTicketComponentImpl which might be interesting….
..I just tested, but this method doesn't prevent double login

zomurn

In fact, we don't have to touch at tomcat session. Parameters need to be set inside the XML file directly authentication-services-context.xml :

<!– The ticket component.                                              –>
    <!– Used for reauthentication                                          –>
    <bean id="ticketComponent" class="org.alfresco.repo.security.authentication.InMemoryTicketComponentImpl">
        <property name="ticketsCache">
            <ref bean="ticketsCache"/>
        </property>
        <!– The period for which tickets are valid in XML duration format. –>
        <!– The default is P1H for one hour.                               –>
        <property name="validDuration">
            <value>P20M</value>
        </property>
        <!– Do tickets expire or live for ever?                            –>
        <property name="ticketsExpire">
            <value>true</value>
        </property>
        <!– Are tickets only valid for a single use?                       –>
        <property name="oneOff">
            <value>false</value>
        </property>
    </bean>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The problem is that, setting like this below, means after 20 minutes of inactivity or activity and *not* only inactivity, the ticket (= session) is expired.

  <property name="validDuration">
            <value>P20M</value>
        </property>
        <!– Do tickets expire or live for ever?                            –>
        <property name="ticketsExpire">
            <value>true</value>
        </property>‍‍‍‍‍‍‍

zomurn

Exactly my problem here :

https://issues.alfresco.com/jira/browse/ETWOONE-74