Optimize openIDConnect providerOptimize openIDConnect providerhttps://liferay.dev/es/c/message_boards/find_thread?p_l_id=119785294&threadId=1234154212026-04-17T18:45:19Z2026-04-17T18:45:19ZRE: Optimize openIDConnect providerJamie Sammonshttps://liferay.dev/es/c/message_boards/find_message?p_l_id=119785294&messageId=1234288912025-06-03T16:55:44Z2025-06-03T16:55:43Z<p>Feature Request Created: https://liferay.atlassian.net/browse/LPD-57065</p>Jamie Sammons2025-06-03T16:55:43ZOptimize openIDConnect providerEric DARIELhttps://liferay.dev/es/c/message_boards/find_message?p_l_id=119785294&messageId=1234154202025-06-03T16:50:53Z2025-05-25T10:52:15Z<p>Hi,</p>
<p>This is a feature request.</p>
<p>For my client, we need to use the idp of the company.</p>
<p>This idp is not very fait and we made an optimisation but it be great
to have it in the liferay module and not in our custom module.</p>
<p>First when we connect, Liferay call the endpoint UserInfo but we have
all ready the infos in the JWT Token (name, firstName and email)</p>
<p>It would be great to have a configuration option (a boolean) to do
the call to the userInfo endpoint or not.</p>
<p>For us we win about 500ms if we do not this at every connection.</p>
<p>Second optimization, sometimes our idp is down. And all our clients
are disconnected by the offlineOpenIdVonnectManager because it tries
to extend the session but the session is not end (it will end in 5
minutes yes) but why close the session if the token is available 5
minutes more ?</p>
<p>Maybe this manager can try 1 minute later another call and close the
session only if it is a forbiden or if the token is outdated but not
if we have a network issue.</p>
<p>Of course this should be configurable in the liferay system (or
instance) configuration like is it for the other options.</p>
<p>Eric.</p>Eric DARIEL2025-05-25T10:52:15Z